[Samba] Samba reporting errors!

[Kevin A. Pieckiel]

My syslog is constantly bombarded with these messages:

Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:get_socket_addr(1012) 
Mar 27 07:15:35 fileserver1 smbd[70359]:   getpeername failed. Error was Socket is not connected 
Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:write_socket_data(499) 
Mar 27 07:15:35 fileserver1 smbd[70359]:   write_socket_data: write failure. Error = Broken pipe 
Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:write_socket(524) 
Mar 27 07:15:35 fileserver1 smbd[70359]:   write_socket: Error writing 4 bytes to socket 12: ERRNO = Broken pipe 
Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:send_smb(704) 
Mar 27 07:15:35 fileserver1 smbd[70359]:   Error writing 4 bytes to client. -1. (Broken pipe) 

I'm running Samba 2.2.8 without optimizations.

#uname -a
FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002     toor at fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1  i386

What do these message mean?  How to I rid myself of them?

Thanks,
Kevin


I'm desperately trying to figure out
why kamikaze pilots wore helmets
-- Dave Edison