Univention Bugzilla – Bug 33031
smbd processes invoked by a user are using user limits for open file handles (1024)
Last modified: 2013-11-04 13:13:47 CET
From Ticket #2013103021001753: In UCS 2.4 a smbd process invoked by a user is running as ruid and euid 0 but uses the max open file limits from samba config (max_open_files). In UCS 3.1 these processes are using the user scope default (1024). Example: 1. Shell (root): while true; do pgrep -f smbd | while read pid; do echo "$pid $(sed -ne 's/Max open files\s\+\([0-9]\+\)\s\+.*/\1/p' < /proc/$pid/limits) $(lsof -n -p $pid | wc -l)"; done; sleep 0.1; ps axo euid,ruid,cmd | grep smbd; done 2. Shell (Administrator): smbclient -L localhost UCS 3.1 1740 32828 97 1770 32828 97 24798 1024 121 (invoked by smbclient) 0 0 /usr/sbin/smbd -D 0 0 /usr/sbin/smbd -D 0 0 /usr/sbin/smbd -D ....... UCS 2.4 5229 16404 83 5235 16404 82 8780 16404 111 (invoked by smbclient) 0 0 /usr/sbin/smbd -D 0 0 /usr/sbin/smbd -D 0 0 /usr/sbin/smbd -D A workaround could be to increase the user scope limit by ucr: security/limits/group/"Domain Users"/soft/nofile security/limits/group/"Domain Users"/hard/nofile
(In reply to Tim Petersen from comment #0) > A workaround could be to increase the user scope limit by ucr: > security/limits/group/"Domain Users"/soft/nofile > security/limits/group/"Domain Users"/hard/nofile Even if the processes are running as euid and ruid 0, increasing the user scope limits will do the trick. I don't know why, but at least it works ;)
Thanks for the useful analysis, I guess this helps solving Bug 32415. *** This bug has been marked as a duplicate of bug 32415 ***