default ulimit -n setting for unraid 5.0?

[sacretagent]

i went today into my go file to change a cron thing that i ave setup a long time ago and was just wondering if this is still necessary

 

ulimit -n  100000;/usr/local/sbin/emhttp &

 

i mean the ulimit-n setting ....

what is the default setting in unraid 5?

is this still in the virgin go file of unraid 5 ?

 

might be time for me to clean out my go files

[garycase]

That hasn't been needed for a long time.

 

It had to do with a bug in v4.6 ... resolved in v4.7 ... that caused errors when writing large numbers of files to the server with Windows to fail due to a queuing problem.    I don't remember the specific details -- but I do know it was fixed in v4.7, and hasn't been a problem since !!

 

[sacretagent]

garycase

 

can you do me a favor and have a look what your outcome is ?

i was never on the 4 series ... not sure why i added it ... or from where it even come LOL

 

[garycase]

It was a fix to the "too many files in use" issue with Windows copies.

 

A quick Google of that issue found this thread, where it was discussed a bit ... the limit suggested there was different than what you have, but it's the same problem.

http://lime-technology.com/forum/index.php?topic=5004.msg95269#msg95269

 

Bottom line:  As I noted above, it was permanently fixed in v4.7 and has not been needed since.

 

Just remove it.

 

[sacretagent]

all i wanted is to know what  ulimit -n outcome was without having to reboot

 

but ok removed the line from my second server and

 

ulimit -n on a stock unraid 5.0 =

 

root@P8H67:~# ulimit -n

40960

 

we will see if we get into trouble or not with nearly 2tb of music files