[Samba] smbd errors in syslog - how to get rid of them?

[David C. Rankin]

Listmates,

	I know the following are harmless, but how do I keep them from filling 
up my syslog? log level = 03. They still appear with log level = 1. Any 
thoughts? The logs:

Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] 
lib/util_sock.c:get_peer_addr(1232)
Jan 23 22:01:30 bonza smbd[16474]:   getpeername failed. Error was 
Transport endpoint is not connected
Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] 
lib/util_sock.c:get_peer_addr(1232)
Jan 23 22:01:30 bonza smbd[16474]:   getpeername failed. Error was 
Transport endpoint is not connected
Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] 
lib/access.c:check_access(327)
Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] 
lib/util_sock.c:get_peer_addr(1232)
Jan 23 22:01:30 bonza smbd[16474]:   getpeername failed. Error was 
Transport endpoint is not connected
Jan 23 22:01:30 bonza smbd[16474]:   Denied connection from  (0.0.0.0)
Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] 
lib/util_sock.c:get_peer_addr(1232)
Jan 23 22:01:30 bonza smbd[16474]:   getpeername failed. Error was 
Transport endpoint is not connected
Jan 23 22:01:30 bonza smbd[16474]:   Connection denied from 0.0.0.0
Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] 
lib/util_sock.c:write_data(562)
Jan 23 22:01:30 bonza smbd[16474]:   write_data: write failure in 
writing to client 192.168.7.143. Error Connection reset by peer
Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] 
lib/util_sock.c:send_smb(769)
Jan 23 22:01:30 bonza smbd[16474]:   Error writing 5 bytes to client. 
-1. (Connection reset by peer)


-- 
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com