On Thu, 5 Dec 2002, Alan W. Rateliff, II wrote: > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: "Van Hoornick Stefaan 999900830" <[EMAIL PROTECTED]> > Cc: "Subscribers of Qpopper" <[EMAIL PROTECTED]> > Sent: Thursday, December 05, 2002 12:01 PM > Subject: Re: qpopper4.0.4 and logging > > > > On 5 Dec 2002, Van Hoornick Stefaan 999900830 wrote: > > > > > Hey, > > > > > > I have the following problem with qpopper 4.0.4 and logging. > > > > > > In fact qpopper is logging notting!!! > > > > > > I used following option at configure > > > --enable-standalone > > > --enable-log-facility=LOG_LOCAL1 > > > --enable-debugging > > > --enable-log-login > > > > > > The syslog.conf file is like this > > > > > > local1.none /var/adm/messages > > > local1.* /var/adm/qpopper.log (And i touched the file) > > > > > > Why is it not logging ?? > > > > You've probably already though of this but something you said makes me > > think you haven't restarted syslogd yet. Syslog creates the files as it > > parses it's config file if they aren't already there. You shouldn't have > > had to create it if syslog had been restarted. That's my take on it. Did > > you restart syslogd? > > That's not always the case with syslogd. On my Solaris boxes, syslog > complains indignantly about files not existing.
I probably should have clarified that a bit with a "GNU" sysklogd. I forgot that part. :) > Try changing the local1.* to local1.debug and see if that helps. I seem to > recall that in the past, using facility.* fails, but *.priority does not. > I've gotten into the habit of using facility.debug instead. > > Also, make sure you have TABs between your left and right sides. local1.* /var/log/pop.log Works for me. And to save me the headache and diskspace of having those messages duplicated for the "messages" log, I add local1.none to its definition. Good point on the tabs. Only allowed whitespace. Justin
