Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 442

2. ~/.profile
3. /etc/bash.bashrc
4. ~/.bashrc
Make custom settings in ~/.profile or ~/.bashrc. To ensure the correct process-
ing of these files, it is necessary to copy the basic settings from /etc/skel/
.profile or /etc/skel/.bashrc into the home directory of the user. It is rec-
ommended to copy the settings from /etc/skel after an update. Execute the following
shell commands to prevent the loss of personal adjustments:
mv ~/.bashrc ~/.bashrc.old
cp /etc/skel/.bashrc ~/.bashrc
mv ~/.profile ~/.profile.old
cp /etc/skel/.profile ~/.profile
Then copy personal adjustments back from the *.old files.
19.1.2 The cron Package
If you want to run commands regularly and automatically in the background at predefined
times, cron is the tool to use. cron is driven by specially formatted time tables. Some
of of them come with the system and users can write their own tables if needed.
The cron tables are located in /var/spool/cron/tabs. /etc/crontab serves
as a systemwide cron table. Enter the username to run the command directly after the
time table and before the command. In
root is entered. Package-specific tables, located in /etc/cron.d, have the same
format. See the cron man page (man cron).
Example 19.1 Entry in /etc/crontab
1-59/5 * * * *
You cannot edit /etc/crontab by calling the command crontab -e. This file
must be loaded directly into an editor, modified, then saved.
A number of packages install shell scripts to the directories /etc/cron.hourly,
/etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly, whose
execution is controlled by /usr/lib/cron/run-crons. /usr/lib/cron/
426 Deployment Guide
Example 19.1, "Entry in /etc/crontab"
root test -x /usr/sbin/atrun && /usr/sbin/atrun
(page 426),