Restart worked. Will try try the cron start/stop next time when I am at the server; as it is remotely located in another country and no technical staff there.
Not sure if this related to the cron daemon error! On trying to start the cron the last time ie before rebooting the server. I typed cron on the SCO server. The comand ran ie it did not give any error - but did not start the cron daemon.
After rebooting the server the users now cannot access the server. They get an error "telnetd: access denied" even before getting log-in prompt. However, I can login directly on the server (locally), but the users cannot access the server via Winet emulator ie using telnet.
I also noted that the cron daemon stopped executing again!!
Please help as this server has been operational for the past 3 years without any problems.
By login locally do you mean at the system console, or at a Windows pc using telnet on the same tcp subnet as the server.
If you are at the console, is tcp running?
Is the system in multi-user mode (can you log on at the console if you press <ctrl><alt><f3>) ?
Have you run out of disk space in the root file system?
Have you run 'authck -a' to test system integrity?
What release of OpenServer are using?
Yes I can, while logging on at the system console. I have noted that sometimes I am able to log-in via telnet. Not sure why but I presume its after a reboot & I am the only user trying.
TCP should be running cause I can ping the server & FTP works. Is there a command to run to see if "TCP" is actually running?
I am able to log on the console multiple times using <Alt> <F2>.
There is space on the root file system.
Please confirm syntax 'authck -a' as this doesnt work.
The SCO version is 5.0, but which release, your answer should have been 5.0.4, or 5.0.6, or 5.0.7
You can get the number from 'uname -X'
'authck' requires root privileges, and is in /tcb/bin, so also check path.
'netstat' will show tcp status with various options