I'm happy to second that finding. I actually tried to run the debugging symbols this morning (before checking email) and it did not work :) The only additional clue I've come up with on this end is that it looks like in at least one instance, the panic action was logged for a computer in the office at the same time that that person's SIP soft phone dropped a call. Samba is running on the same office server as asterisk (phone pbx software), though I've just set asterisk to run at a higher priority than samba.
Should the debugging symbols produce more than this in the panic email sent to me? The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 32373 (/usr/sbin/smbd). Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1213294912 (LWP 32373)] 0xb7f0a410 in ?? () #0 0xb7f0a410 in ?? () #1 0x00000001 in ?? () #2 0x00000000 in ?? () -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
