Thank you all,<br>This will definitely a help.<br><br>Regards,<br>Kapil<br><br><br><div class="gmail_quote">On Jan 10, 2008 11:16 AM, Markus Peuhkuri <<a href="mailto:puhuri@iki.fi">puhuri@iki.fi</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Carsten Aulbert kirjoitti:<br><div class="Ih2E3d">><br>> As Michael said: Pretty off-topic, but the hint can be found in the<br>> syslogd man-page (version 1.4.1, Debian package sysklogd):<br>><br></div>Hi, in case you make driver development, the syslog process may not be
<br>able to deliver all messages (like one in kernel OOPS). In that case<br>you may want to check netconsole kernel module; check<br>$KERNEL_SOURCE/Documentation/network/netconsole.txt, or use serial cable<br>and start kernel with command line console=ttyS0,57600 (for example).
<br><br>rgds, Markus<br><br></blockquote></div><br>