Segmentation fault at boot

Chris Lingard chris at
Sun Oct 20 10:01:31 PDT 2002

Simon Comeau Martel wrote:

>> When you have done this; open two windows
>> Do  /etc/rc.d/rc3.d/S10sysklogd  stop
>> From the source directory of sysklog
>> source /etc/sysconfig/rc
>> source $rc_functions
>> ./syslogd -m 0 -d
>> In the other window
>> gdb  klogd
>> run  -d  -n
>> If it fails try the comands list and bt within gdb;  bt is back trace
> Allocated parts table for 1024 file descriptors.
> Starting.

> restart. Called fprintlog, logging to FILE /var/log/sys.log
> syslogd: restarted.
> Debugging disabled, SIGUSR1 to turn on debugging.

> Starting program: /home/simon/Linux/Construction/sysklogd-1.4.1/klogd -d 
> -n Logging line:

> Loading kernel module symbols - Size of table: 4055
> Logging line:
>         Line: Loaded %d %s from %d module%s
>         Priority: 6

That sys log is working.  That is normal debug output from the -d
The -n in klogd stops it releasing the terminal.  You will be able
to see messages being appended to /var/log/sys.log

Suggest you install this version then try and make it fail.

Both can be run from /usr/sbin. You can do
/etc/rc.d/rc3.d/S10sysklogd  stop
and/etc/rc.d/rc3.d/S10sysklogd  start

If this fails you can check the flags -d and -n in the man pages
of klogd and syslogd.  Just repeat the stop, then run it under debug.

gdb  /usr/sbin/klogd
run  -d          or just plain run
and try and make it fail


Unsubscribe: send email to listar at
and put 'unsubscribe lfs-support' in the subject header of the message

More information about the lfs-support mailing list