On my Debian system running Samba 3.0.23, nmbd sends a lot of log messages to the system log at "error" priority when it starts up. There are a total of 44 lines, including messages like: Oct 3 20:15:52 eagle nmbd[8656]: ***** Oct 3 20:15:52 eagle nmbd[8656]: Oct 3 20:15:52 eagle nmbd[8656]: Samba server EAGLE is now a domain master browser for workgroup ENDBRACKET on subnet 192.168.1.254 Oct 3 20:15:52 eagle nmbd[8656]: Oct 3 20:15:52 eagle nmbd[8656]: ***** I noticed this when trying to set up automated notification of important error messages by sending log messages at error priority or higher to my mobile phone by SMS. As you can imagine, I got a lot of SMSs. Samba's syslog support says that the Samba debug levels should be mapped to syslog priorities as follows: 0 = error 1 = warning 2 = notice 3 = info 4+ = debug This seems to be more or less followed by most of Samba, but not very well by nmbd.
Created attachment 2170 [details] modify log levels in nmbd source code The attached patch aims to fix the most obvious and frequently occurring messages. After it is applied, only error messages will be logged at LOG_ERR, while other messages will be logged at more appropriate (lower) priorities so they can be handled properly in /etc/syslog.conf.
Is there any update on this? Do you need me to do something more?
This bug was referenced in samba master: b6049a30127ee3851faad62b4b57d1e8e674bc98 5181b1c8cb653d9085a1d55a1fe69f8526ce9123 2fbd773a515fe4b5e1e26a250d64d69019947b7d 1186ec227daf09e60fbd6a53ce54506d04fe7a65
will be fixed with the upcoming 4.19 relrease