![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| cron job starts new cron proccess | ron76 | SUN Solaris | 3 | 05-11-2008 10:07 PM |
| AIX and cron logs filtering ?: /etc/cronlog.conf, /var/adm/cron/log | Keith Johnson | AIX | 0 | 01-09-2008 05:32 PM |
| Stoping & starting the cron daemon | othman | SCO | 0 | 04-30-2007 07:23 AM |
| Cron daemon | karine | UNIX for Dummies Questions & Answers | 3 | 11-18-2004 08:22 AM |
| daemon | bat_oyu | High Level Programming | 1 | 10-16-2001 07:57 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
||||
|
||||
|
Cron Daemon
Hey all,
I'm running Mandrake 7.2 with several of the development/server tools loaded and operating. One problem I'm having is that I keep getting emails from the "Cron Daemon". They all say: touch: /var/log/news/nntpsend.log: Permission denied chmod: same as above /usr/bin/nntpsend: same as above Can someone explain what the Cron Daemon is and what it does? I mean, I know what daemon's are, but I can't figure out what this one is used for and how to configure it, if necessary. I'm also getting another email from the same daemon reporting the following: DB2 problem...: missing or empty key value specified /usr/bin/news.daily: /var/lib/news/ .news.daily: Permission denied Reading active file failed, exiting, (see syslog for more info). Has fetchnews been run? I'm guessing by that, this has something to do with a news reporting daemon... but anyways, I want to stop the errors. If anyone can help, it would be appreciated. Thanks ahead of time. Ben |
| Forum Sponsor | ||
|
|
|
#2
|
|||
|
|||
|
The cron daemon is the daemon which deals with job scheduling in UNIX. Jobs are scheduled via a flat ASCII text file called a crontab. If something goes wrong with a job that has been scheduled with cron then it usually sends a mail to the user concerned - check your crontab file for jobs that are running (crontab -l) edit it if need be (crontab -e).
The jobs that are running will give you better idea of where to goto troubleshoot the actual problem. If you can't see any jobs scheduled bear in mind that a crontab can exist for any users, so su to a user you suspect would run a job and check their crontab file. Regards. |
|
#3
|
||||
|
||||
|
Thanks. Currently, this is a box that only I work on, and most of the time I work as root.
|
||||
| Google The UNIX and Linux Forums |