Re-4: Soekris net4501 & syslogd

[openbsd@sybrespace.de]

Argh ;o)

Thanx a lot guys, that was the problem indeed. I forgot to link /dev/log
to the newly created /tmp/log socket. Could beat me myself for that!

Thanks for all the comments!

Jens

> Do you have a symlink /tmp/log -> /dev/log since I guess that is where
> for example logger want to write to.
> 
> $ ktrace logger -t hej hej
> $ kdump | grep -C "/dev/log" 
>   4589 logger   RET   sigprocmask -65793/0xfffefeff
>   4589 logger   CALL  connect(0x1,0xcfbf9d9c,0x6a)
>   4589 logger   NAMI  "/dev/log"
>   4589 logger   RET   connect 0
>   4589 logger   CALL  sigprocmask(0x1,0xffffffff)
> $ 
> 
> openbsd@sybrespace.de writes:
> 
> > As mentioned before, I already did start it with the -d option and tried to
> > use the "logger" command with no result. The debug output states nothing.
> > And I copied an original syslog.conf from a working machine over, so that
> > shouldn't be the problem.
> > Any other idea?
> >
> > Thanks, Jens
> >
> > -------- Original Message --------
> > Subject: Re: Soekris net4501 & syslogd (03-Mrz-2004 3:58)
> > From:    rd@thrush.com
> > To:      openbsd@sybrespace.de
> >
> >> >>>>> "o" == openbsd  <openbsd@sybrespace.de> writes:
> >> o> I'm currently working on a setup for a Soekris net4501. Now that 
> works
> >> o> quite impressivly but at the moment I have trouble getting pppoe to 
> work.
> >> 
> >> o> The other problem is, that can't debug nor see the output of 'ppp' 
> >> because
> >> o> syslogd isn't writing anything in its log files except for start, 
> >> restart an
> >> o> shutdown messages. The system was created with Chris' flashdist and 
> >> modified
> >> o> as needed based on OpenBSD 3.4 stable.
> >> o> I tried using 'logger' to create entries in the message log but no 
> luck 
> >> here.
> >> o> The syslog.conf I use is the following:
> >> 
> >>   There are no tab characters in your file.  If the copy in your email
> >>   matches /etc/syslog.conf, then you'll have the behavior you have
> >>   described.  If it's not a tab problem, kill syslogd and start it
> >>   manually with the additional -d flag.  That may guide you closer to
> >>   the problem.
> >> 
> >> Regards, Bob