Arkadiusz BubaĆa
2012-Jul-27 14:11 UTC
[Samba] Samba 3.6.x: smbd receives sigpipe and crashes
Hello, I've got problems with Samba 3.6.0 up to 3.6.6. Forked smbd processes are closing unexpectedly and sometimes smbd server exits. (In Samba 3.5.16 everything works). When invoke smbd from gdb and turn off SIGPIPE passing (by command "handle SIGPIPE nostop nopass") everything works fine. I found out that SigBlk flag of forked smbd processes in /proc/*/status is: 0000000000000880 and should be 0000000000001880 (It works in Samba 3.5.16). This flag changes after invoking getpwnam function, after passing string "guest+workgroup" to it. There is probably a memory leak or something. Does anyone have similiar problem? Thank you in advance -- Best regards Arkadiusz Buba?a Open-E Poland Sp. z o.o. www.open-e.com
Jeremy Allison
2012-Aug-03 19:43 UTC
[Samba] Samba 3.6.x: smbd receives sigpipe and crashes
On Fri, Jul 27, 2012 at 04:11:53PM +0200, Arkadiusz Buba?a wrote:> Hello, > I've got problems with Samba 3.6.0 up to 3.6.6. Forked smbd > processes are closing unexpectedly and sometimes smbd server exits. > (In Samba 3.5.16 everything works). > When invoke smbd from gdb and turn off SIGPIPE passing (by command > "handle SIGPIPE nostop nopass") everything works fine. I found out > that SigBlk flag of forked smbd processes in /proc/*/status is: > 0000000000000880 and should be 0000000000001880 (It works in Samba > 3.5.16). > This flag changes after invoking getpwnam function, after passing > string "guest+workgroup" to it. > There is probably a memory leak or something. > > Does anyone have similiar problem?What platform are you running Samba on ?