Problem
On a system in "High" security mode, after installing or removing OSS642A, the Cron Supplement, I get mail messages from cron which contain:
cron: can't set login UIDand cron jobs don't appear to run.
Cause
OSS642A attempts to restart /etc/cron after installation or removal
of itself. It does not do this properly, and as a result, both
crontab(C) and at(C) jobs fail to run at their scheduled times, if
the system is configured in high security mode. The mail message
above from cron accompanies each failed attempt by cron to start
the desired job. Solution
This problem has been reported to SCO Engineering and will be
fixed in a future revision of OSS642. Use one of the following
workarounds to resolve the problem with OSS642A:1. Install (remove) OSS642A from single-user mode, or reboot the machine after installing (removing) it. Cron will subsequently be started properly upon going to multi-user mode.
2. If you have already installed or removed OSS642A, run the following commands as root to avoid having to reboot the system:
/etc/init.d/cron stop
rm -f /usr/lib/cron/FIFO
if grep -q "^TCBFILES=OFF" /etc/default/security; then
cron
else
sd cron
fi