I run samba 2.0.6 on Sun ultra enterprise 2 server.
Lately the logs have been filled with
[1999/11/29 20:11:19, 0] lib/util_sock.c:write_socket_data(537)
write_socket_data: write failure. Error = Broken pipe
[1999/11/29 20:19:31, 0] lib/util_sock.c:write_socket_data(537)
write_socket_data: write failure. Error = Broken pipe
[1999/11/29 20:24:39, 0] lib/util_sock.c:write_socket_data(537)
write_socket_data: write failure. Error = Broken pipe
[1999/11/29 20:31:03, 0] lib/util_sock.c:write_socket_data(537)
write_socket_data: write failure. Error = Broken pipe
Things seem to work but I'm a little worried.
What is the problem here?
This samba is bound to hme0 but I have a samba.2.1-alpha running
on another virtual interface, hme0:2, as PDC.
/Ul
I have similar experience with this appearing in workstation logs for both NT (4.0 sp5) and w95. They began to appear about 4-5 weeks ago after we applied several y2k related patches to Solaris 2.6 on both Ultra 1 and Sparc 10 (running Samba 2.0.5a before and after patch application). The log entries seem to reoccur at a 6 minute time interval. Coincidence or cause and effect?>>> Ulf Noren said:> I run samba 2.0.6 on Sun ultra enterprise 2 server. > Lately the logs have been filled with > > [1999/11/29 20:11:19, 0] lib/util_sock.c:write_socket_data(537) > write_socket_data: write failure. Error = Broken pipe > [1999/11/29 20:19:31, 0] lib/util_sock.c:write_socket_data(537) > write_socket_data: write failure. Error = Broken pipe > [1999/11/29 20:24:39, 0] lib/util_sock.c:write_socket_data(537) > write_socket_data: write failure. Error = Broken pipe > [1999/11/29 20:31:03, 0] lib/util_sock.c:write_socket_data(537) > write_socket_data: write failure. Error = Broken pipe > > Things seem to work but I'm a little worried. > What is the problem here? > > This samba is bound to hme0 but I have a samba.2.1-alpha running > on another virtual interface, hme0:2, as PDC. > > /Ul