Bug 1359 - syslog messages from read_socket_data have too high a priority level
syslog messages from read_socket_data have too high a priority level
Status: RESOLVED WONTFIX
Product: Samba 3.0
Classification: Unclassified
Component: File Services
3.0.2a
All Linux
: P5 trivial
: none
Assigned To: Samba Bugzilla Account
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-18 02:47 UTC by Alan J. Wylie
Modified: 2005-02-11 07:39 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan J. Wylie 2004-05-18 02:47:12 UTC
My logs are full of messages

May 13 13:57:19 frogserver smbd[19440]: [2004/05/13 13:57:19, 0]
lib/util_sock.c:read_socket_data(365) 
May 13 13:57:19 frogserver smbd[19440]:   read_socket_data: recv failure for 4.
Error = Connection reset by peer 

which seem to be logged at a syslog priority of "err"

These messages seem to be fairly boring, and not indicative of a
failure withing Samba. Could the syslog priority level be reduced to
"warning", "info" or "debug"?

http://lists.samba.org/archive/samba/2001-December/033191.html
http://lists.samba.org/archive/samba/2002-April/041735.html
http://lists.samba.org/archive/samba/2004-April/083915.html
Comment 1 Gerald (Jerry) Carter 2005-02-11 07:39:46 UTC
These can be pretty important.  You might wanmt to refer to bug 1257
for some details on how to prevent XP clients from generating 
so many messages.

Out logging does need to be overhauled, but is lower on the 
priority list at the moment.