syslog basic querry

[alfred hitch]

Hi Wolfgang,

Thanks for tip on unchanged-stats, it's exactly what I was looking for.
May be i will patch busybox tail for it, should be helpful patch IMHO.

pramfs from it's web page looked like meant for NVRAM based logging ?
I didnt quite fully get u-boot thing you pointed.
If I understand it well, that you are saying that u-boot can be told
to leave out an area of RAM (from clearing / init'ing it ?)  ? and so
memory snapshot will be retained across boots ?

This  should work across processor generated resets .. But, will it
fail if say there has been an external reset pin triggered. External
button reset will send reset / power cycle not only processor but also
all peripherals ?

Regards,
Alfred

On 12/27/05, Wolfgang Denk <wd at denx.de> wrote:
> In message <20051227174704.80990.qmail at web413.biz.mail.mud.yahoo.com> you wrote:
> >
> > This would happen on any unix machine.  The tail program
> >  never reopens the file being monitored.  So when syslogd
>
> It depends. See the "--max-unchanged-stats" option with GNU tar which
> handles exaclty cases like this one.
>
> >   If you can log to another machine that would be best.
> >
> >  Otherwise you have to write to the flash.  You could write a
>
> ... or to some other persistent memory. If you  use  U-Boot  as  boot
> loader,  you  can  make  the  syslog buffer persistent, i. e. it will
> survive crashes and reboots. Also, you can use ome RAM for  a  pramfs
> file systeme which can survice a reboot as well.
>
> Not to mention that there are other hardware  solutions  like  static
> RAM, FRAM, etc.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Due to lack of disk space, this fortune database has been discontinued.
>