tags 311300 wontfix thanks John, maybe a samba documentation issue for you, below...
Quoting Andrew Bartlett ([EMAIL PROTECTED]): > On Wed, 2005-06-01 at 05:04 -0500, Christian Perrier wrote: > > We will deal with it with the Samba Team. Thanks for reporting. > > > > > > Let's first get attention of Andrew Bartlett who follows the Debian > > BTS : Andrew, is it expected that "syslog only = 1" and "syslog = 1" > > still triggers the smbd and nmbd initialisation logged to log.smbd and > > log.nmbd? > > > > In short, bug or feature? > > > > If this is a bug, I'll send it to bugzilla... > > > > If this is a feature, I'll write a short note to Jon Terpstra to get > > it mentioned in the So Fine Documentation. > > It is a feature, that is Samba's startup code runs before the smb.conf > is processed. One could argue that it is a bug, but I would argue it is > also WONTFIX. If we delay logging until after smb.conf processing, we > could not log incorrect smb.conf statements. OK, so John, there seems to be some little thingie to add to the Already Wonderful Samba Documentation�(as long as it is not already documented of course) : As mentioned in http://bugs.debian.org/311300, samba logs in log.smbd and log.smbd even when "syslog only = 1" and "syslog = 1" in smb.conf. As mentioned by Andrew above, this is because the code which processes smb.conf comes after the code which starts logging. This is indeed also why some logging occurs to the default logfiles even when these files are requested to go elsewhere on the filesystem in smb.conf Is this behaviour already documented somewhere? > > Certainly don't let this get in the way of sarge... Obviously, yes...
