I have 2 Gentoo boxes and both seem to have a problem that I'd like to track down. On shutdown and on boot both show an error: /sbin/runscript.sh: line 35 2 : : Command not found /sbin/runscript.sh: line 36 2 : : Command not found I asked a friend about it and he decided to reboot his Gentoo box He has it too. It doesn't seem serious as I can't find anything that won't work that I can tie to it but the message is annoying as, especially on a boot, it is repeated 100 or so times.
please provide more input ... like after what messages do you see these errors ?
Please include the baselayout version, as well as a copy of /sbin/runscript.sh.
Not sure is this is related but rather than start a new bug, I'll attach here: Seems all init.d scripts display: /sbin/runscript.sh: line 76: fg: no job control when running, either at system startup or when running them manually. All scripts seem to run ok. sys-apps/baselayout-1.8.5.8 emerged on 1/24 .. noticed messages this AM after rebooting system. I'll attach runscript.sh. Thanks
Created attachment 7724 [details] /sbin/runscript.sh: line 76: fg: no job control
baselayout version is 1.8.5.8 error is repeated on shutdown after shutting down random seed shutting down dhcpd and others and on boot, among several others: bringing up lo bringing up random # generator bringing up eth0 bringing up syslogd,klog I will attach /sbin/runscript.sh
Created attachment 7728 [details] Ernie's /sbin/runscript.sh
As for the first problem .. line 35 and 36 is comments ..., so wierd one :/ For the job control one .. bash detects if the OS supports it. Could be a glibc/kernel problem I guess. What kernel ?
yeah, wierd as hell but I'm not seeing the error that Dave has.The fact remains, though I have an error that seems to mean nothing on 3 of 4 Gentoo boxes.
Maybe try to remerge glibc/bash ? Also check that you do not have too aggressive CFLAGS when doing this ...
could you try to re-emerge baselayout (just to eliminate a possible problem in the /sbin/runscript.sh file) - previous 'comment' lines in the file have been processed without problem, so problem with bash/glibc is unlikely.
Hey, I get this bug too at startup and shutdown. Same as above ecept like: /sbin/runscript.sh: line 35 1 : : Command not found /sbin/runscript.sh: line 36 2 : : Command not found A one instead of a two?! Machine type : Athlon XP, CCFLAGS = -march-athlon-xp -O3 -something else I forgot I tried removing the commands after the comment block starting on line 35, because I figured whatever is parsing runscript.sh would ignore lines beginning with \n and # right? It didn't change a thing, but its a thought. Chris Janscen.
Similarly, I get xdm|kde "command not found" at runscript.sh line 53 after adding xdm to the default runlevel (depends on whether I have xdm or kdm in /etc/rc.conf). The error occurs at each invocation of runscript.sh during the boot process.
I am at baselayout 1.8.5.8
Hmm, just had an idea .. please attach your /etc/rc.conf.
Created attachment 8344 [details] hmmm lines 35 & 36
Yep, you need to add '1' and '2' to PROTOCOLS="..." line ..... Please close this if you changed /etc/rc.conf and it is fixed, thanks.
BTW, I adjusted the comments in /etc/rc.conf to try and prevent this.
Comments in /etc/rc.conf is fixed to be much clearer, so this should be fixed.
