From Fedora Project Wiki
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
|description=run-parts is able to run scripts in a directory. The command run-parts is used for cron.daily jobs. | |description=run-parts is able to run scripts in a directory. The command run-parts is used for cron.daily jobs. | ||
|setup=Run command ''tail -f /var/log/cron'' in one terminal (as root). | |setup=Run command ''tail -f /var/log/cron'' in one terminal (as root). | ||
|actions=As root try to execute run-parts | |actions=As root try to execute run-parts without options. Pay attention to directory, which you'll run. For example prelink in /etc/cron.daily runs quite long. You might need create your own directory with test files. | ||
# Execute: ''run-parts /etc/cron.daily'' | # Execute: ''run-parts /etc/cron.daily'' | ||
|results=Scripts in your directory were executed. | |results=Scripts in your directory were executed. | ||
Revision as of 08:15, 4 January 2011
Description
run-parts is able to run scripts in a directory. The command run-parts is used for cron.daily jobs.
Setup
Run command tail -f /var/log/cron in one terminal (as root).
How to test
As root try to execute run-parts without options. Pay attention to directory, which you'll run. For example prelink in /etc/cron.daily runs quite long. You might need create your own directory with test files.
- Execute: run-parts /etc/cron.daily
Expected Results
Scripts in your directory were executed.
- This can be verified by checking /var/log/cron, where are logged starting/finishing of jobs eg:
Jan 4 08:39:47 hostname run-parts(/etc/cron.daily)[3204]: starting tmpwatch
Jan 4 08:39:47 hostname run-parts(/etc/cron.daily)[6432]: finished tmpwatch