My printer works ok under samba 2.0.7 but from time to time (about
twice a say) users can't print.
I found this in logs:
[2001/04/09 21:20:38, 2] smbd/connection.c:utmp_claim(560)
utmp_claim: conn NULL
[2001/04/09 21:20:38, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2001/04/09 21:20:38, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 7: ERRNO = Broken
pipe
[2001/04/09 21:20:38, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
[2001/04/09 21:20:48, 2] smbd/connection.c:utmp_claim(560)
utmp_claim: conn NULL
[2001/04/09 21:20:48, 0]
lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2001/04/09 21:20:48, 0] lib/util_sock.c:write_socket(566)
write_socket: Error writing 4 bytes to socket 7: ERRNO Broken pipe
[2001/04/09 21:20:48, 0] lib/util_sock.c:send_smb(754)
Error writing 4 bytes to client. -1. Exiting
[2001/04/09 21:23:50, 2]
smbd/connection.c:utmp_claim(560) utmp_claim: conn NULL
If I restart Samba, everything works ok again and users can print.
This is my printer entry:
[Panasonic KX]
#comment = Panasonic KX de S2
public = Yes
path = /tmp
create mask = 0700
printable = Yes
browseable = Yes
printing = BSD
#printer = lp
guest ok = yes
guest account = s2
map to guest = bad password
Anybody know what this is about?
--
______________________________
Daniel de los Reyes
S2-Selling Soluciones
Valencia Spain
e-mail: dadecal@s2-selling.com
Powered by Debian GNU-Linux 2.2r2
______________________________
