default logging output

[Andrew Bartlett]

On Fri, 2011-07-08 at 10:43 +1000, Andrew Bartlett wrote:
> On Wed, 2011-07-06 at 10:48 +0200, Michael Adam wrote:
> > Hi Andrew,
> > 
> 
> > This does not seem to be true. Running make test, I see logs of
> > this on standard output/error:
> > 
> > [2011/07/06 10:35:35,  0] ../lib/util/debug.c:572(reopen_logs_internal)
> >   Unable to open new log file '/data/samba/install/master/var/log.smbd': Permission denied
> > 
> > I am running "make test" (from source3) as non-root and the log file
> > /data/samba/install/master/var/log.smbd is the compiled-in
> > location of the log file in the install path. Now I have done
> > "make install" as root. So the permission is correctly denied.
> > 
> > The bug is that daemons started by "make test" try to open or
> > access those logs at all. "make test" should run completely
> > self-contained without accessing the install path at all.
> 
> Indeed, the indication to log to stdout on the command line is meant to
> override all subsequent log directives.  I'll chase this down. 

I don't see this in the top level 'make test', but I certainly did see
issues with the logging not being set to stdout after the fork().  The
attached patches seems to fix that.  (We closed stdout).

> > My suspicion is that the recent debug and dynconfig changes broke
> > it. (I am not able to monitor all changes in the merging area
> > lately. It is just too much, so I am going to report problems
> > once I stumble across.)
> > 
> > What is more, why do smbd/nmbd/winbindd log to standard output (or error)
> > at startup as of recently? This his horrible! Firstly it clutters
> > make test output, making it mostly unreadable (for me), and secondly,
> > this should not happen when starting productive daemons either.
> > At least I am used to reading the debug output from the logs.
> 
> Where would you like startup errors (such as a failure to parse the
> smb.conf) to go?  If we log them to the default log file, then we may
> put startup logs in one file, possibly in the wrong place, and then once
> smb.conf is loaded (possibly from a registry tdb), we would start
> logging to a completely different place.

I've set logging to go to stdout until redirected to a logfile.  But
currently that is the default logfile until the smb.conf is processed.

Andrew Bartlett

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-lib-util-Change-debug-priority-order-DEBUG_STDOUT-no.patch
Type: text/x-patch
Size: 960 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20110718/d592d4a1/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-debug-log-early-messages-to-stdout-and-keep-it-open.patch
Type: text/x-patch
Size: 4369 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20110718/d592d4a1/attachment-0001.bin>