Samba Log Level Change in recent version (Debian Squeeze)?

[Arno Schäfer]

Hi,

I recently upgraded to Debian Squeeze (and with it, upgraded to a new 
Samba version) and since then, I have been seeing these syslog messages:

Mar  8 12:55:43 aschaefer smbd[2348]: [2011/03/08 12:55:43.520515,  0] 
smbd/nttrans.c:2204(call_nt_transact_ioctl)
Mar  8 12:55:43 aschaefer smbd[2348]: 
call_nt_transact_ioctl(0x1401c4): Currently not implemented.

Mar  8 03:37:57 aschaefer smbd[20075]: [2011/03/08 03:37:57.034618,  0] 
lib/util_sock.c:474(read_fd_with_timeout)
Mar  8 03:37:57 aschaefer smbd[20075]: [2011/03/08 03:37:57.034977,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Mar  8 03:37:57 aschaefer smbd[20075]:   getpeername failed. Error was 
Transport endpoint is not connected
Mar  8 03:37:57 aschaefer smbd[20075]:   read_fd_with_timeout: client 
0.0.0.0 read error = No route to host.
Mar  8 03:37:57 aschaefer smbd[20075]: [2011/03/08 03:37:57.035237,  0] 
lib/util_sock.c:680(write_data)
Mar  8 03:37:57 aschaefer smbd[20075]: [2011/03/08 03:37:57.035273,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Mar  8 03:37:57 aschaefer smbd[20075]:   getpeername failed. Error was 
Transport endpoint is not connected
Mar  8 03:37:57 aschaefer smbd[20075]:   write_data: write failure in 
writing to client 0.0.0.0. Error Broken pipe
Mar  8 03:37:57 aschaefer smbd[20075]: [2011/03/08 03:37:57.035378,  0] 
smbd/process.c:79(srv_send_smb)
Mar  8 03:37:57 aschaefer smbd[20075]:   Error writing 75 bytes to 
client. -1. (Transport endpoint is not connected)


My log settings are:

         log level = 0
         syslog = 1
         syslog only = No
         log file =


Now I have read that these are not really anything to worry about, and 
everything appears to be working fine. I would be interested:

- I have never had these errors in Debian Lenny - has the log level of 
these messages been changed at some point? The current version according 
to dpkg is

2:3.5.6~dfsg-3squeeze2

- if I interpret my configuration correctly, log level 0 is only errors 
(LOG_ERR). Why are these messages logged as errors, if they commonly 
occur in Windows networks and do not appear to indicate any problems?

BTW. if this a Debian issue, feel free to shout at me :-)

Best Regards,

Arno

-- 
Arno Schäfer
IT-Beratung & Softwareentwicklung

PHP - Java - Web-Anwendungen
Linux/Unix - MySQL - Hochverfügbarkeit - Security

Weilbornstraße 10 - 63303 Dreieich
mailto: arno_schaefer at gmx.de