/dev/null and init

Frank Tiemann ft at sinneswandel.de
Mon Jul 16 05:06:41 PDT 2001


hi *

>> hm, if i start the script manualy - there's no output at all (even in
>> the  logfiles)
>
> I assume that the module in question is already loaded at that point.  If
> so, insmod would not load the module again, and in fact will tell you so
> ("insmod: a module named xxx already exists").  However, you redirected
> stdout and stderr to /dev/null in your script, so it's no surprise you
> encountered no messages whatsoever.

i've unloaded the module before - so, the msgs should be the same, 
shouldn't they?

>> inittab:
>> slog:12345:respawn:/usr/sbin/syslogd -n -r -f
>> /system/sysconfig/syslog.conf klog:12345:respawn:/usr/sbin/klogd   -n -c
>> 1 -x
>>
>> this should be enough to start the *logd /befor/ the network, shouldn't
>> it?
>
> You'd also have to ensure that the above lines come /before/ the line that
> start the rc script for the appropriate runlevel.  Otherwise, /all/ your
> startup scripts will be run first, then syslogd/klogd.  As you can
> imagine, that'll lose you a lot of startup logs.

--------------------------
si::sysinit:/system/init.d/rcS
slog:12345:respawn:/usr/sbin/syslogd -n -f /system/sysconfig/syslog.conf
klog:12345:respawn:/usr/sbin/klogd   -n -c 1 -x
l0:0:wait:/system/init.d/rc 0
--------------------------

this should be ok, i think...

> The syslogd '-r' flag may cause problems, too, since it tries to bind a
> socket before your network's set up.  Syslogd may not abend in this case,
> but you'll likely lose the ability to accept remote syslog messages.

hm, syslog starts without problems. but i never tested the remote 
functionality...

> - Adrian


frank




-- 
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message



More information about the lfs-dev mailing list