[BusyBox] Problem with syslogd

[Jason]

OK, I know this is a stretch, but it's all I can think of because other
then this one difference, it looks like what I got working.  Change the
/dev/log link from ../var/run/syslog.socket  to /var/run/syslog.socket.
So give it the full path not relative to anything and see ,what happens.

-- 
       Jason
www.jasonandjessi.com
It gimme the jibblies

On Thu, 20 Nov 2003, Stewart Brodie wrote:

> Jason <jason at jasonandjessi.com> wrote:
>
> > For giggles, could you paste an ls -l and file on the actual dev and the
> > sym link ?
>
> No problem.  Apologies for the wrap on the symlink.  The date anomolies are
> expected - it's running in +0800 timezone and all things untouched since the
> rdate in the boot sequence are dated Jan 1 2000 :)
>
>
> # ls -al /dev/log /var/run
> lrwxrwxrwx    1 1375     1375           24 Nov 17 23:07 /dev/log ->
> ../var/run/syslog.socket
>
> /var/run:
> drwxr-xr-x    2 root     root         1024 Nov 21 01:06 .
> drwxr-xr-x   17 root     root         1024 Jan  1  2000 ..
> -rw-r--r--    1 root     root            4 Nov 21 01:06 cron.pid
> -rw-r--r--    1 root     root            4 Jan  1  2000 nscd.pid
> srw-rw-rw-    1 root     root            0 Jan  1  2000 syslog.socket
>
>
>