Re: samba Unmatched Entries
Willi Mann <[email protected]>
| Newsgroups | gmane.comp.log.logwatch.devel |
|---|---|
| Message-ID | <[email protected]> |
> These are debug entries from a debug log, and it looks to me, based on > this report, that the samba service filter wasn't designed to handle > debug messages. This seems odd, as the samba log file group config was > by default pointing to where the debug logs are stored. (Normally samba > logging is done through syslog. The samba log file group config doesn't > even look at the syslog logs.) > > Briefly looking at the service filter code, it does look like there are > some expressions to match debug entries, so I'm not sure why there are > so many unmatched entries, unless the filter was designed for a > different samba version, or an expectation of a lower debug level. I guess on most distributions, syslog does not get successful logins, so the filter author had to use the debug logfiles. I've quickly searched the syslog logfiles on one of my servers, but there are no messages from samba in Debian default config. All messages are in /var/log/samba/*. AFAIK the samba filter was written long before the 3.0 release, so it was written for the messages samba typically wrote out in 2.2 (or maybe earlier). So it would be cool if someone brave rewrites it :-). Willi