syslog basic querry
alfred hitch
alfred.hitch at gmail.com
Mon Jan 2 06:38:44 UTC 2006
Hi,
I am sorry but I couldnt get some aspects of your reply.
My requirement / question: How to design a syslog / klogd handler, so
that I can get my traces from programs / crashes after reboot also.
Delayed writes is one solution and problem in it is that it will loose
up data on crash.
You mentioned on some kernel knob which can be used for synchronus
write ? even in case of a kernel crash/ hang ?
More generally, asking how do most of embedded boxes are designed to
handle such logging cases ? How to get logs from a machine on field
which is rebooting without putting a ip based syslog server access ?
Regards,
Alfred
On 12/31/05, Rob Landley <rob at landley.net> wrote:
> On Tuesday 27 December 2005 00:21, alfred hitch wrote:
> > I am surprised noone has observed this. Is everyone using a big log
> > file on their boxes ?
>
> In my case I don't use syslogd at all.
>
> > 2) If one is to not write to flash very often for log messages. How
> > does one works around to get messages across reboots for crashes /
> > other info etc ?
> > delayed writes (again will miss out of last cycle before crash ?)?
>
> You have a conceptual problem here. If you want to delay and batch writes
> from a filesystem to the underlying block device, laptop mode does what you
> want already. But if you're worried that a crash will happen between the
> time a log entry is generated and the time it gets written out, then you have
> to write it out before the crash might happen.
>
> The kernel gives you this knob. Twiddling this knob merely exchanges one kind
> of suck for another.
>
> > Regards,
> > Alfred
>
> Rob
> --
> Steve Ballmer: Innovation! Inigo Montoya: You keep using that word.
> I do not think it means what you think it means.
>
More information about the busybox
mailing list