Mailinglist Archive: opensuse-factory (1233 mails)

["Richard (MQ)" <osl2008@xxxxxxxxxxxxxx>]

Carlos E. R. wrote:
> On Thursday, 2008-11-27 at 15:17 +0200, Silviu Marin-Caea wrote:
>
> > That is such a baroque improvisation for remote logging!  This wheel
> > has been
> > invented before, and it's a little rounder that this :-)
>
> That implementation is done when you want to get the direct file logs
> that Yast creates during installation; as the installation system runs
> from a DVD, the logs are made to memory, and only if installation
> succeeds they are copied to the final installed system, on disk. An
> alternative is to log those to an usb stick, I think.

As you say - /var/log is on ram-disc during installation and readily
lost if things go wrong. This "baroque improvisation" is actually quite
easy to implement, and it does work. I can't see how syslog-ng might be
used here, the YaST messages aren't readily routed to the network are they?

> But it is of no use for kernel debugging.
>
> > syslogd has an option that allows it to receive logs from a remote
> > system.
> > See the man page of syslog and /etc/sysconfig/syslog
>
> Correct. I do receive syslog messages from my router in this system, as
> a matter of fact. However, during a kernel failure the network is not
> guaranteed to work... and it doesn't.

I hadn't realised that you wanted some tool to allow you to talk to the
machine _after_ the kernel crash. Indeed my suggestion is quite useless
for that. I wasn't aware that such a thing was even possible (and also
surprised that it might be of any use, after the event).
-- 
Cheers
Richard (MQ)
-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx