Yes, i have seen a lot of similar bug reports too, but all of them were unresolved.
When the problem appeared we checked a lot of configuration issues. The problem seems NOT to be user or client specific. The users where the PANIC appeared: - had a unix account - a samba account with the same uid - no special ulimits set - no group membership which seems to be responsible for the problem - su <user> did work, opening files as this user did work, no messages like: to many open files... # getent passwd 11789 diehl:x:11789:11700::/home/diehl:/bin/bash # pdbedit -L -u diehl diehl:11789: # su - diehl -c 'ulimit -u' 30720 # getent group 11700 <groupname>:x:11700: # net groupmap list | grep <groupname> <groupname> (<SID>) -> <groupname> Samba worked without any problems if there were less than about 100 clients/users connected. Volker Lendecke from SerNet proposed to set "change notify = no" as a workaround, which we did not really test. If you need more information, please let me know, but since this server acts as a domain controller in an productive environment I cannot reproduce the bug. -- samba PANIC: failed to set uid https://bugs.launchpad.net/bugs/341816 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
