SAMBA 2.2.4 or 2.2.7a and broken pipe
Carl Gunnar Linden, MSL Stockholm Sweden.
linden at msia02.msi.se
Wed Feb 26 09:49:27 GMT 2003
I am running OpenVMS V7.3 and
Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 1
I try to run SAMBA 2.2.4 or 2.2.7a. It works with TCPIP V5.3-18 but
I think it stopped working since I applied the TCPIP_ECO V5.3-181 patch.
I can connect by using SMBCLIENT. If I try from Windows 95, for example,
I get the following written to the log-file
[2003/02/25 17:12:15, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(1018)
getpeername failed. Error was socket is not connected
[2003/02/25 17:12:16, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(505)
write_socket_data: write failure. Error = broken pipe
[2003/02/25 17:12:16, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(529)
write_socket: Error writing 4 bytes to socket 3: ERRNO = broken pipe
[2003/02/25 17:12:16, 0] DKA200:[SAMBA.SOURCE.LIB]UTIL_SOCK.C;8:(709)
Error writing 4 bytes to client. -1. (broken pipe)
Has anybody else seen something like this and what is a broken pipe?
Thankfull for any hint.
Carl Gunnar Linden
MSL
Stockholm
Sweden
More information about the samba-vms
mailing list