rc3 runlevel 3

PMP · 07-29-2009, 05:21 AM

I have a script that has following lines

echo "Here you are press any key to print next line"
read var
echo "This is the next line"

I have kept this script in /etc/rc3.d/

Now when system goes to runlevel 3 it executes the prompt but it does not wait for return key. It immediatly prints the next line. I want it to hold on till I press enter.

Is there any way to do it.

PMP · 07-29-2009, 07:54 AM

Any clues

timvandijk039 · 07-29-2009, 07:59 AM

Hi PMP,

Tested your problem under Debian and the following worked for me.

Make test.sh script in /etc/init.d with the following shell code

Code:

#!/bin/sh
case "$1" in
	start)
		echo "Interactive test at startup"
		read var
		echo ${var}
		;;

	stop)
		echo "Interactive test at shutdown"
		read var
		echo ${var}
		;;

esac

After that create a link in the appropriate /etc/rc*.d (debians default runlevel is 2, Fedora's runlevel usually is 3 or 5)

Code:

ln -s /etc/init.d/test.sh S90test.sh

Of course you can do the same for the shutdown sequence, for example:

Code:

ln -s /etc/init.d/test.sh K10test.sh

That's it. Works like a charm.

Hope this helps.

catkin · 07-29-2009, 09:46 AM

Quote:

Originally Posted by PMP

Now when system goes to runlevel 3 it executes the prompt but it does not wait for return key. It immediatly prints the next line.

Interesting! timvandijk039 gave the pukka way of setting up a boot script but your script should work the way you set it up. The "read" should not return until it has read a line of input from stdin. Probably it did so. Might be interesting to print var in the message: echo "This is the next line. var is '$var'". The single quotes will help in case var contains only whitespace characters. Probably it is an empty line and the terminating line-end will have been stripped off so it will be empty. You could set var to something before the "read"; then, if var is empty after the "read" you would know the "read" had read an empty line.

Which distro are you using? Maybe some distros feed stuff to init scripts on stdin in case they are "badly" coded and try to read stdin which would hang boot -- which, I guess, is exactly what you are trying to do!

You may be able to find out where stdin is coming from by

Code:

ls -l /proc/$$/fd/0

What are you trying to achieve? If you want to pause boot then a symlink to /sbin/sulogin works nicely (ignore the error message about "start").

Best

Charles

PMP · 07-29-2009, 02:00 PM

I am using solaris. I want to reboot it just after the my script finishes. but want user to know that the system is going to reboot. want a halt. but thats not happening.

catkin · 07-29-2009, 02:04 PM

Quote:

Originally Posted by PMP

I am using solaris. I want to reboot it just after the my script finishes. but want user to know that the system is going to reboot. want a halt. but thats not happening.

Good to know. Maybe we can progress that if you try some of my suggestions.