Technical article 115442

Cron jobs don't run after installing OSS642A on a system in high security mode.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

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 UID

and 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

From the Xinuos technical article database, record 115442. Reproduced with permission. The original is at www.sco.com/ta/115442, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.