SCO License security - another flame

[Peter da Silva]

In article <1174 at pemcom.pem-stuttgart.de> ralfi at pemcom.pem-stuttgart.de (Ralf U. Holighaus) writes:
> mju at mudos.ann-arbor.mi.us (Marc Unangst) writes:
> >They did do something about it; it just wasn't enough.  I still can't
> >log in as root, kill cron, and then restart it.  The newuser program I

> Ever heard of the crontab command? That correctly updates the cron tables
> in the /usr/spool/cron/crontabs directory WITHOUT problems. Thats the clean
> way.  Not the quick'n dirty one.

That's nice. Can you change cron's environment, timezone, umask, etc.. that
way? Tell it that the system time has changed? Etc... there's lots of reasons
to restart cron other than to rescan the crontabs.

(and why the hell are those crontabs in spool in SV? They should be in lib)
-- 
Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180;
Sugar Land, TX  77487-5012;         `-_-' "Have you hugged your wolf, today?"