I'm writing automated test scripts for SCO 5.x and UnixWare 2.x and 7.x. I would like to know how to automatically login (as root) after a reboot (user and password). The problem is that during these test, which I run from the /etc/rc2.d directory, I need to check the status of the system. If I try to login during these test it takes FOREVER, if at all, before I can login (extremely heavy load on OS). It would be helpful if I could somehow login before I start these tests. This would be for testing purposes only so I am not concerned about any security. Any help as to which file to edit or how to set this up would be greatly appreciated. I am fairly proficient around these O/Ss. Thanks!

James, Sorry I never came back to you before (rather busy and all that). Just to make it clear, you want to run the tests automatically after a reboot but you want to login first. If this is the case then within the /etc/rc2.d directory create a script called S99myjob with the contents: echo "/mydir/mytest > mylog" | at now + 5 minutes This will not start you job until five minutes after the reload and therefore giving you plenty of time to login. Regards, Anthony.

Hmmmm .... maybe I should clarify what my tests do Anthony. I am testing a RAID controller with extremely heavy I/O. After a certain amount of time the tests will reboot the system and start performing other tests (this reboot is necessary because a new configuration is on the RAID controller). After the reboot the test scripts start the heavy I/O again ... at this point I am probably at a bar hoisting a few and not very concerned about returning to the system to login. Any other ideas?

James, This bodge will work only if you have a spare machine. On the machine you are working on setup a .rhosts in the root directory with the remote machine name in it. Then on the remote machine run the following script: while true do rlogin testmachine sleep 10 done This means it will automatically login when the system comes up and will retry when the system is reloaded until it comes back up again. If you do not have a spare machine then let me know as I am working on a similar problem myself and I am trying it through port monitors but I haven't had much success yet. Regards, Anthony.

That sounds simple enough to work! We have plenty of spare machines around here so that shouldn't be a problem. And in the script you gave I could just add all the other machine names too. This will be a good temporary solution, but please let me know if you figure out how to do it on the test machine itself. Thanks and keep me updated! James