--- Comment #12 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Shawn McKinney from comment #10)
(In reply to Quanah Gibson-Mount from comment #9)
> (In reply to Shawn McKinney from comment #8)
> > >logfile <filename>
> > >Specify a file for recording slapd debug messages. By default these
messages >only go to stderr, are not recorded anywhere else, and are unrelated to
>messages exposed by the loglevel configuration parameter. Specifying a logfile
>copies messages to both stderr and the logfile.
> > Confused by phrasing "and are unrelated to messages exposed by the
> > configuration parameter". How are they unrelated to the loglevel setting?
> It's talking about slapd debug messages, which are separate from loglevel
> "Specify a file for recording slapd debug messages."
> > IOW - Doesn't loglevel always control the granularity of the messages,
> > regardless of whether they are bound for stderr or the logfile?
> No, only loglevel messages, not debug messages.
I must be way off the mark because my assumption, 'debug', we're talking
about what gets routed to the (new) logfile.
stderr messages are routed to syslog.
In light of that, possibly faulty assertion, the loglevel setting controls
the level of granularity sent to the debug log (in addition to syslog), per
e.g. set loglevel 0, and no messages will be sent. loglevel -1 sends all.
What do I have wrong here?
That's entirely backward. debuglevel controls messages to stderr. loglevel
controls messages sent to syslog.
The confusing part is that logfile specifies a file to receive debug messages,
in addition to stderr.
And then the logfile_only directive means debug messages only go to the
logfile, and turns off writing to stderr.
And then, because some pinheads are too stupid to use debuglevel and still want
to use loglevel, but without syslog, the logfile_only directive additionally
routes loglevel messages to the logfile instead of syslog.
You are receiving this mail because:
You are on the CC list for the issue.