DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Choosing an upgrade path

Upgrading cron and at jobs

If you upgrade from a system that uses /usr/lib/cron/cron.deny instead of /usr/lib/cron/cron.allow, then both files will exist on the system after an Upgrade installation. To continue using /usr/lib/cron/cron.deny, you should remove /usr/lib/cron/cron.allow. (If you are using /usr/lib/cron/cron.allow, you do not need to change.)

Similarly, if you upgrade from a system that uses /usr/lib/cron/at.deny instead of /usr/lib/cron/at.allow, then both files will be present after the upgrade, and you should remove /usr/lib/cron/at.allow. (If you are using /usr/lib/cron/at.allow, you do not need to change.)

Upgrading a system with user crontab(C) entries might produce an error message similar to:

Error:  Unable to add custom symlinks report to crontab file

Press <Enter> to ignore this error message and continue; your crontab files will be preserved during the Upgrade installation.


Next topic: Upgrading Netscape FastTrack
Previous topic: Missing user-created files

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003