Bug 23335 – After updating world, shell scripts report commands not found

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Squee 2003-06-23 11:05:02 UTC]

I did 'emerge -u world' today (June 23), and then etc-update (replacing all of
the init.d scripts) and now many bash scripts, such as rc-update, /sbin/rc, etc.
report the following errors over and over again:

bash: line 42: will: command not found
bash: line 67: entrance: command not found

The scripts still seem to complete correctly. I can't seem to find out exactly
where these errors are coming from, so I can't give much more information.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Martin Schlemmer (RETIRED) 2003-06-23 16:16:04 UTC]

Please run:

 # grep -r entrance /etc/*

and report output.

[Comment 2 Squee 2003-06-23 17:43:17 UTC]

# grep -r entrance /etc/*
/etc/apache/lib/python2.2/test/test_zlib.py:       Of entrance to a quarrel, but being in,
grep: /etc/apache/lib/X11/mwm: No such file or directory
/etc/apache/lib/mozilla/include/msgcompose/nsMsgSend.h:  PRBool  mAbortInProcess;              // Used by Abort to avoid reentrance.
Binary file /etc/apache/lib/aspell/en-only.rws matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnome-stones.so.0.0.0 matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnome-stones.so.0 matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnome-stones.so matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnome-stones.a matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnomekoban.so.0.0.0 matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnomekoban.so.0 matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnomekoban.so matches
Binary file /etc/apache/lib/gnome-stones/objects/libgnomekoban.a matches
/etc/init.d/xdm:                        EXE="$(which entranced)"
/etc/init_d.old/xdm:                    EXE="$(which entranced)"
/etc/rc.conf:entrance ]
/etc/runlevels/default/xdm:                     EXE="$(which entranced)"

After seeing this about, it looks like rc.conf was to blame...Going into rc.conf I found that two comment lines had wrapped. I've fixed it, but this may be indicative of a problem with etc-update...?

[Comment 3 Martin Schlemmer (RETIRED) 2003-06-23 21:16:31 UTC]

So you havent edited it, except for running etc-update from where it worked
find to where it broke ?

[Comment 4 Squee 2003-06-24 09:55:10 UTC]

Except for editing rc.conf to fix the problem, no I haven't changed it except for etc-update.

[Comment 5 Martin Schlemmer (RETIRED) 2003-06-30 14:16:59 UTC]

Ok, so we can safely say its due to a type-o in rc.conf.  Marking as
fixed.