Hello, Dbmail logs via syslog, and you can adjust the verbosity of what it logs in dbmail.conf. Probably your syslogd is setup to print messages on the console or to some tty, which is usually set in /etc/syslogd.conf (but if your don't find anything there, check the manpage for your syslogd server). If you can't figure out how to get it setup the way you want, post back with the contents of your syslog.conf (you can strip all commented lines if you want), and describe what you want it to do/not do, and we can probably help get you going.
jn ---- Original Message ---- From: Bill Hacker <[email protected]> To: [email protected] Subject: [Dbmail-dev] Console Messages Sent: Sun, 30 Nov 2003 17:25:58 +0800 > Odd one here: > > I have (AFAIK) all err, warning, emerg, debug, and such messages that > would ordinarily be thrown onto the console redirected in syslogd to > various /var/log<files> ...which I can then 'tail -f' in a separate > login console... Handy.. > > But - invoking a daemon on as-yet-not-fully-configured installation, to > wit: dbmail-pop3d or dbmail-imapd - results in an error condition > (which is not what I am posting about - the *error condition* and its > 'warning' messages are quite legitimate at this stage...) > > What escapes me is that these error message still appear on the console. > > It would appear that syslogd is not being used, *but*.... > > I do not see anything in dbmail.conf that specifies either syslog or any > other method of logging. > > Q: Where should I look, and/or is this a compile-time option that cannot > be changed at runtime? > > Bill Hacker > > > > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > -- End Original Message -- -- Jesse Norell jesse (at) kci.net
