SCO

Hello - We have setup printers to startup in the /etc/rc.d/8 directory and when the SCO system is booted this script should kick them off or start them up but it doesn't. So I have to start it from root and leave the window open. I know this isn't right and trying to figure out what's missing. In the /var/adm/rc2.log it shows:

/etc/rc.d/8/userdef: /dev/ttyr031: cannot open
/etc/rc.d/8/userdef: /dev/ttyr030: cannot open
/etc/rc.d/8/userdef: /dev/ttyr028: cannot open
/etc/rc.d/8/userdef: /dev/ttyr029: cannot open
/etc/rc.d/8/userdef: /dev/ttyr027: cannot open

Can someone tell me how to fix this?

Thank you!

Not sure (have no experience with SCO) but it could be that your script is being started before the device driver has been loaded or before some other necessary component has been started. Try putting your script inside /etc/rc.d/rc.local, which is usually where post-startup scripts go. On most linux distributions and solaris, the scripts inside such a directory are numbered, S10network, S20http-server, etc., so that the OS runs them in order.

Hi - thanks for responding. I do not have the rc.local under /etc/rc.d; any other suggestions? Here's what I have:

drwxr-xr-x 2 root sys 512 Oct 22 1999 0
drwxr-xr-x 2 root sys 512 Oct 22 1999 1
drwxr-xr-x 2 root sys 512 Oct 22 1999 2
drwxr-xr-x 2 root sys 512 Oct 22 1999 3
drwxr-xr-x 2 root sys 512 Oct 22 1999 4
drwxr-xr-x 2 root sys 512 Oct 22 1999 5
drwxr-xr-x 2 root sys 512 Oct 22 1999 6
drwxr-xr-x 2 root sys 512 Oct 26 1999 7
drwxr-xr-x 2 root sys 512 Oct 8 10:21 8
drwxr-xr-x 2 root sys 512 Oct 22 1999 9

Does each correspond to an init level??

Yes; however I noticed that we had a few problems with the terminal settings and had to change a couple. I think 2 are not named correctly in the file. I will verify this again later today and make sure. Still if only 2 are wrong why didn't the other ones work? Right now, I have to start the file "userdef" in a root window and leave the window open after the system is rebooted. I know this is not right. This was orginally setup by one of our hardware vendors and when I brought it to his attention, he said he checked everything and does not know any reason why this won't work. So for now, I make sure daily this window does not close. The hardware vendor is still trying to figure this out as well. Hope you can help!

Thats because you executed the program in an interactive shell... You should in this case use

Code:

nohup <command/prog> &

Do those devices exist?

What is your init default (or runlevel)?
(who -r on most unix)

You should have a /etc/inittab, what is there?