May 8, 201511 yr After a lot of experimenting I found a solution for my NFS connected Bluray player to play ISOs and rips without stuttering and sound breakups. To establish this I had to lower the nfsd max_block_size to 4096. I used these commands in the CLI: /etc/rc.d/rc.nfsd stop echo 4096 > /proc/fs/nfsd/max_block_size /etc/rc.d/rc.nfsd start I now want this to survive a reboot. Adding these lines to the end of the go file resulted in an error that /proc/fs/nfsd/max_block_size wasn't found. Was this because all services weren't started yet? Should there be a delay added before these lines get executed? Or is there a better way to make it survive a reboot. BTW, when I executed these lines a little later in telnet there were no errors.
May 8, 201511 yr I'm not sure if this will work but if you have the powerdown.plg installed then you can created a S00.sh script with the commands above. I believe that the S00 script occurs later on in the boot process.
May 8, 201511 yr Author I don't know when /proc/fs/nfsd/max_block_size is created. My guess is after the array disks are mounted, shares are up and NFS started. Is there a way to check if /proc/fs/nfsd/max_block_size is available or that it gets created with the value I want? Can S00.sh be placed in the root of the flash disk?
May 8, 201511 yr Can S00.sh be placed in the root of the flash disk? The powerdown package forum page gives you all the instructions. The S00.sh file lives on the flash disk under the plugin folder.
Archived
This topic is now archived and is closed to further replies.