On Thu, 15 Apr 2004, Doug Koobs wrote:
> > Hi,
> >
> > I'm using 2.2.3 and had no trouble with syslogd, I use
> > local6.* instead of
> > local6.debug.
> > By the way local0 through local7 are made available by syslog
> > to applications
> > wishing to have a separate log file (man syslog.conf
> Since upgrading Cyrus imapd to 2.2.3, there have been no entries in
Logging has changed in 2.2. The logging facility can now be configured at
compile time and at least my rpms do it with '--with-syslogfacility=MAIL'.
That said you may have a closer look at how your cyrus got compiled.
Simon
>
> Hi,
>
> I'm using 2.2.3 and had no trouble with syslogd, I use
> local6.* instead of
> local6.debug.
> By the way local0 through local7 are made available by syslog
> to applications
> wishing to have a separate log file (man syslog.conf should
> tell you more).
>
> If local6.* doesn't chan
Hi,
I'm using 2.2.3 and had no trouble with syslogd, I use local6.* instead of
local6.debug.
By the way local0 through local7 are made available by syslog to applications
wishing to have a separate log file (man syslog.conf should tell you more).
If local6.* doesn't change anything you should tr
> I've just had something similar, it was down to spacing in the
> syslogd.conf file, it really didn't like spaces - needed to be tabs. I
> think this is due to the file be parsed by m4.
>
> Neil.
Thanks Neil,
The local6.debug line was not using tabs, just a space, so I rewrote the
line using t
I've just had something similar, it was down to spacing in the
syslogd.conf file, it really didn't like spaces - needed to be tabs. I
think this is due to the file be parsed by m4.
Neil.
On Thu, 2004-04-15 at 16:04, Doug Koobs wrote:
> Since upgrading Cyrus imapd to 2.2.3, there have been no ent
