Sponsored Content
Full Discussion: crond
Top Forums UNIX for Dummies Questions & Answers crond Post 55534 by hassan2 on Tuesday 14th of September 2004 08:57:47 AM
Old 09-14-2004
you proberly do have any cron job schedule that the reason cron deamon is not running.

crond starts automatically, when there is a cron job in crontab.
To list jobs in crontab issue this command
Code:
crontab -l

to schedule job to run at 3:10am issue command
Code:
crontab -e

and then add a line, something like:
Code:
10 3 * * * /path_to your_backup_script

cron deamon lives in /usr/sbin/cron but this could be different on your system. crond will start automatically once a job has been schedule.

To find where your cron deamon lives issus command
Code:
find / -name cron 2>/dev/null


Last edited by Yogesh Sawant; 02-27-2010 at 01:17 PM.. Reason: added code tags
 

4 More Discussions You Might Find Interesting

1. Red Hat

redhat 5.2 tikanga crond running but not reading crontab file

Issue:crond is running, can even restart it and /var/log/cron shows it starting. The /etc/crontab file is correct as compared to another machine. I set the crontab file to enter a datestamp into a file under /tmp every minute. Thing is, the crontab file is not being read or cron is not working... (12 Replies)
Discussion started by: robjmarquez
12 Replies

2. Red Hat

/usr/sbin/crond: can't lock /var/run/crond.pid,

please tell pre-requisite steps to activate cron. i activated the cron but it not executing the script which i set in crontab entry.through root user i passed the service crond start it get start.but when i go to etc/init.d and passed crond stop command.it gets crond: can't lock /var/run/crond.pid,... (2 Replies)
Discussion started by: umair
2 Replies

3. UNIX for Dummies Questions & Answers

crond not work after writing to cron log?

Yesterday I was testing out some cron commands and when i was check the /var/log/cron with vi editor I accidentally did :wq instead. Since then the log has not updated and I'm assuming no cronjob is running because looking at the log there's activities everyday there's some default stuff that... (5 Replies)
Discussion started by: orionoreo
5 Replies

4. UNIX for Advanced & Expert Users

crond: Authentication token is no longer valid; new one required.

Hi can any one please help me with this there are some cron jobs running on one of production servers i noticed the jobs are not running for long time, when i checked the logs i founf this message, information form the server # chage -l root Minimum: 0 Maximum: 99999... (2 Replies)
Discussion started by: robo
2 Replies
CRONTAB(1)						    BSD General Commands Manual 						CRONTAB(1)

NAME
crontab -- maintain crontab files for individual users (V3) SYNOPSIS
crontab [-u user] file crontab [-u user] { -l | -r | -e } DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have their own crontab, and they are not intended to be edited directly. (Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8), which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.) If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the /usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the /usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com- ments. The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given. The following options are available: -u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you should always use the -u option for safety's sake. -l Display the current crontab on standard output. -r Remove the current crontab. -e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified crontab will be installed automatically. FILES
/usr/lib/cron/cron.allow /usr/lib/cron/cron.deny DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line. SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1) STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. AUTHORS
Paul Vixie <paul@vix.com> BSD
December 29, 1993 BSD
All times are GMT -4. The time now is 02:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy