Denys, thanks for your reply. I also noticed that /dev/log was missing. Attached the trace for strace logger "hello" greg
________________________________ De : Denys Vlasenko <[email protected]> À : [email protected] Cc : greg h <[email protected]> Envoyé le : Jeudi, 14 Mai 2009, 0h06mn 41s Objet : Re: syslogd+ /var/log/messages file empty On Wednesday 13 May 2009 15:19, greg h wrote: > Hi all, > Here is my configuration: > Platform : arm-at91 (sam9260) > Kernel: 2.6.28.1 > Buildroot: 2009.02 > Busybox: 1.13.2 > > I noticed a problem with regards to the /var/log/messages file. > Indeed this file is well created at startup but it is never updated (the size > of this file is always at 0) > > my inittab > # Logging junk > null::sysinit:/bin/touch /var/log/messages > null::respawn:/sbin/syslogd -n -m 0 > null::respawn:/sbin/klogd -n > tty3::respawn:/usr/bin/tail -f /var/log/messages > > any ideas ? Maybe something mounted and populated a fresh ramfs-based /dev ? This way, old /dev/log is inaccessible, but syslogd doesn't know that! What do you see when you do "strace logger Hello"? -- vda
strace
Description: Binary data
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
