- To: email@example.com
- Subject: /etc/init.d/rcS
- From: Elizabeth Barham <firstname.lastname@example.org>
- Date: 02 Aug 2002 03:12:48 -0500
- Message-id: <email@example.com>
- In-reply-to: "Chris Tillman"'s message of "Thu, 1 Aug 2002 18:09:29 -0700"
I managed to crash my system playing around with esd and on the
re-boot I noticed an odd err concerning /etc/init.d/rcS:
for i in /etc/rcS.d/S??*
# Ignore dangling symlinks for now.
[ ! -f "$i" ] && continue
case "$i" in
# Source shell script for speed.
trap - INT QUIT TSTP
# No sh extension, so fork subprocess.
some of /etc/rcS.d/
lrwxrwxrwx 1 root root 19 Jan 11 2002 S30setserial -> ../init.d/setserial
lrwxrwxrwx 1 root root 19 Jan 11 2002 S35devpts.sh -> ../init.d/devpts.sh
lrwxrwxrwx 1 root root 21 Jan 11 2002 S35mountall.sh -> ../init.d/mountall.sh
lrwxrwxrwx 1 root root 19 Jan 11 2002 S39dns-clean -> ../init.d/dns-clean
lrwxrwxrwx 1 root root 18 Jul 21 04:18 S39ifupdown -> ../init.d/ifupdown
lrwxrwxrwx 1 root root 21 Jan 11 2002 S40hostname.sh -> ../init.d/hostname.sh
As soon as it finishes mountall.sh, it tries dns-clean, which causes a
SEGFAULT, and displays the line with "$i start" from above.
It runs hostname.sh correctly. In fact, it all runs fine except
dns-clean and ifupdown and this happens on a regular basis; this has
the unfortunate side-effect of making the networking sub-system think
that the interfaces are up later on during the boot sequence when they
are truly not up.
Any ideas on what might be causing this?
Thank you, Elizabeth