Wait, but:
if (config_get_value("trace_level", service_name, trace_level) < 0)
trace(TRACE_FATAL, "%s,%s: error getting config!",
__FILE__, __func__);
Oh, cute:
/* FIXME: Always returns 0, which is dandy for debugging. */
int config_get_value(const field_t field_name,
Guess this should be part of the trace cleanup project, too... ;-)
Aaron
On Fri, 2005-12-16 at 17:04 +0100, Paul J Stevens wrote:
> There're not fatal. But when they are missing there's no logging at all!
> Which effectively hides the cause of any fatal errors :-)
>
> Aaron Stone wrote:
> > That's dumb, why are those TRACE_FATAL when not found? I just copied it
> > twice more to the new options; I don't think any failure to find the
> > TRACE_* config options should be FATAL, just result in sane defaults.
> >
> > I'll make it part of my trace-fixing project to fix that!
> >
> > Aaron
> >
> > On Fri, 2005-12-16 at 11:44 +0100, Paul J Stevens wrote:
> >
> >>Add:
> >>
> >>TRACE_SYSLOG=1
> >>TRACE_STDERR=0
> >>
> >>to your dbmail.conf as documented in the example config.
> >>
> >>This one had me stumped as well last week :-(
> >>
> >>
> >>
> >>
> >>Oleg Lapshin wrote:
> >>
> >>>Hello.
> >>>I compiled dbmail rev 1940.
> >>>Run dbmail-imapd and .... no messages at all.(TRACE_LEVEL=5)
> >>>no forking, no work.
> >>>
> >>>I attach output from "strace dbmail-imapd -n -v" command
> >>>(only "dbmail-imapd -V" and "dbmail-imapd -h" give me output)
> >>>
> >>>
> >>
> >
> > _______________________________________________
> > Dbmail-dev mailing list
> > Dbmail-dev@dbmail.org
> > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> >
>
