[Samba] FW: Samba 2.2.4 Error Messages

[Doug.M.Flack at rolls-royce.com]

Samba Team,

We are running Samba 2.2.4 on a Solaris 7 system and are seeing the attached
messages. What do these messages mean? Samba seems to be working correctly.
What should we do to keep these messages from being generated?

Thanks,

Douglas Flack (317-230-6417)

-----Original Message-----
From: Douglas M. Flack 230-6417 [mailto:ï?àï?x at agt.gmeds.com]
Sent: Wednesday, May 29, 2002 11:21 AM
To: doug.m.flack at rolls-royce.com
Subject: Samba 2.2.4 Error Messages


We are receiving the following messages from Samba 2.2.4 on a Solaris 2.7 
system. Any ideas as to the cause and fix?

  Copyright Andrew Tridgell and the Samba Team 1992-2002
[2002/05/29 08:49:17, 0] lib/util_sock.c:(1010)
  getpeername failed. Error was Transport endpoint is not connected
[2002/05/29 08:49:17, 0] lib/util_sock.c:(497)
  write_socket_data: write failure. Error = Broken pipe
[2002/05/29 08:49:17, 0] lib/util_sock.c:(522)
  write_socket: Error writing 4 bytes to socket 12: ERRNO = Broken pipe
[2002/05/29 08:49:17, 0] lib/util_sock.c:(702)
  Error writing 4 bytes to client. -1. (Broken pipe)
[2002/05/29 09:21:19, 0] lib/util_sock.c:(1010)
  getpeername failed. Error was Transport endpoint is not connected
[2002/05/29 09:21:19, 0] lib/util_sock.c:(497)
  write_socket_data: write failure. Error = Broken pipe
[2002/05/29 09:21:19, 0] lib/util_sock.c:(522)
  write_socket: Error writing 4 bytes to socket 5: ERRNO = Broken pipe
[2002/05/29 09:21:19, 0] lib/util_sock.c:(702)
  Error writing 4 bytes to client. -1. (Broken pipe)
[2002/05/29 09:53:19, 0] lib/util_sock.c:(1010)
  getpeername failed. Error was Transport endpoint is not connected
[2002/05/29 09:53:19, 0] lib/util_sock.c:(497)
  write_socket_data: write failure. Error = Broken pipe
[2002/05/29 09:53:19, 0] lib/util_sock.c:(522)
  write_socket: Error writing 4 bytes to socket 12: ERRNO = Broken pipe
[2002/05/29 09:53:19, 0] lib/util_sock.c:(702)
  Error writing 4 bytes to client. -1. (Broken pipe)
[2002/05/29 10:25:19, 0] lib/util_sock.c:(1010)
  getpeername failed. Error was Transport endpoint is not connected
[2002/05/29 10:25:19, 0] lib/util_sock.c:(497)
  write_socket_data: write failure. Error = Broken pipe
[2002/05/29 10:25:19, 0] lib/util_sock.c:(522)
  write_socket: Error writing 4 bytes to socket 5: ERRNO = Broken pipe
[2002/05/29 10:25:19, 0] lib/util_sock.c:(702)
  Error writing 4 bytes to client. -1. (Broken pipe)
This email message and any attachments are for the sole use of the intended
recipients and may contain proprietary and/or confidential information which
may be privileged or otherwise protected from disclosure. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipients, please contact the sender by reply email and destroy
the original message and any copies of the message as well as any
attachments to the original message.