syslog basic querry

alfred hitch alfred.hitch at gmail.com
Thu Dec 29 03:17:22 UTC 2005


I need a meachanism where in I can see the logs / what was going on
just before a reboot / crash / kernel hang.

Any suggestions on how one can do this ?

Alfred

On 12/28/05, Rushi Lala <rushi.lala at gmail.com> wrote:
> Alfred,
>
> Do you want to use  the logs for your debugging purpose ? or you want to
> keep it as a feature in the system ?
> If its just for debugging for you then you can pass a kernel parameter
> to get kernel logs out via serial port and also you can do the same with
> syslog from init.d.
>
> Or you might want to log everything via network on some other machine.
>
> I never tried tail when syslog rolls the old logs so i don't know. The
> only quick thing i seen is that if the empty message file is not
> available my application does not log any thing to /var/log/messages.
>
> alfred hitch wrote:
>
> >>Reset is fine, no matter if it's caused by a soft reboot  or  a  hard
> >>reset. You will lose the log buffer when power cycling,ou w though.
> >>
> >>
> >
> >Alfred:
> >In my system, hardware guys have a power cycle issued on a watchdog expiry.
> >Is it normal ? reason given to me is that unless there is a power
> >cycle peripherals will not reset ? Is it normal ?
> >In current case, I believe RAM contents will be lost for sure wont they be ?
> >
> >And, if not, any known issues in having reset line driven high by
> >external watchdog  circuitry instead of power cycle ?
> >I had seen long time back for example a bug with flash that unless you
> >power cycle , if flash happened to be in some read mode or something
> >it will remain so, if there was just a processor reset.
> >Does flash for example has a RST pin ? If yes, then it should take
> >care of this ?
> >
> >Regards,
> >Alfred
> >
> >
> >
>
>



More information about the busybox mailing list