Our Samba/CUPS based printserver loses the info of which driver belongs to a certain printer. The server is running Samba 3.2.7 on Solaris 9.
The workstation from which printerdrivers are uploaded runs from a VMware server VM (XP) which is reverted to the last snapshot every time, to have a clean machine. The smb log shows:
[2009/01/20 16:30:50, 0] lib/fault.c:(40) =============================================================== [2009/01/20 16:30:50, 0] lib/fault.c:(41) INTERNAL ERROR: Signal 10 in pid 20404 (3.2.7) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/01/20 16:30:50, 0] lib/fault.c:(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/01/20 16:30:50, 0] lib/fault.c:(44) =============================================================== [2009/01/20 16:30:50, 0] lib/util.c:(1663) PANIC (pid 20404): internal error [2009/01/20 16:30:50, 0] lib/util.c:(1817) unable to produce a stack trace on this platform [2009/01/20 16:30:50, 0] lib/fault.c:(201) dumping core in /var/log/samba/cores/smbd I guess this is bad....Unfortunately, there is no core dump in that directory. Any comments? -Remy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
