03-13-2008
Restart cron.
Instead of killing the daemon and starting it. Use /etc/init.d/cron stop and /etc/init.d/cron start.
OR
if you just wish to refresh the cron daemon to reread the entries give HUP signal to cron daemon.
#kill -HUP PID #### (PID is for cron daemon)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm a newbie to the Unix world Help!
I have to maintain a host of Sybase database servers sitting on Unix Sun Solaris 8...I've been tasked with finding/creating a way to auto start/stop Unix via unix commands, specifically when the Unix servers need to be restarted we want Sybase to start... (2 Replies)
Discussion started by: jjv1
2 Replies
2. Solaris
As the title. Thanks (1 Reply)
Discussion started by: eddsos
1 Replies
3. Shell Programming and Scripting
Hi All,
I have requirement. I am running a job every 30mins. before starting the process, i need to check the process, if the process is still running then i need not trigger the process again, if it is not running then trigger the process again. I am using cron to trigger the shell script. Can... (7 Replies)
Discussion started by: srinivas_paluku
7 Replies
4. UNIX for Advanced & Expert Users
Dear all,
Is it possible to view all the cronjobs set under all the userids in a server.
Or view all the cronjobs in the server?
Thanks in anticipation,
Sree. (2 Replies)
Discussion started by: Sreejith_VK
2 Replies
5. Linux
Hi,
When I googled, I came to know that I can not call the command
"service <service-name> start" from cron, insted I have to specify path to the service-name.
I wanted to know the reason.
Thanks,
Hansini (3 Replies)
Discussion started by: hansini
3 Replies
6. Solaris
There are two jobs in Solaris , Cron and at jobs..
I know how to disable or enable cron jobs.
How can I enable at jobs and disable it.
Kindly help.
Rj (2 Replies)
Discussion started by: jegaraman
2 Replies
7. Shell Programming and Scripting
Hi,
Anyone can help me on how my script will run on crontab, When I manually run my script, it work. But when I put in cron didn't work.
#crontab schedule
00 16 * * * /home/scriptdir/myscript.sh
# myscript.sh
#!/bin/bash
echo "mypassword"| sudo -S /etc/init.d/vpnclient_init start
cd... (2 Replies)
Discussion started by: fspalero
2 Replies
8. Shell Programming and Scripting
Hi All,
Please provide the command to stop all the cron jobs.
Thanks in Advance
Regards,
Sindu (2 Replies)
Discussion started by: indira_s
2 Replies
9. UNIX and Linux Applications
Good afternoon
I need your help please.
There is a Mantenance Windos which needs to Restart de Database Server 192.x.x.97 to set up some configuration
Is it mandatory or not to stop/start Applcation server that runs in 192.x.x.95 ?
Is it mandatory or not to stop/start apache and Tomcat?... (3 Replies)
Discussion started by: alexcol
3 Replies
10. Shell Programming and Scripting
Hi,
I need to create a shell script for automated server patching, with the following scenario:
I have two Linux servers Primary and secondary.
Server patching should start on Primary 1st and then secondary.
1st check both servers are up and running.
Then stop primary and patching will... (1 Reply)
Discussion started by: rcroyal88
1 Replies
cron(8) System Manager's Manual cron(8)
NAME
cron - The system clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
The cron daemon runs shell commands at specified dates and times. Commands that are to run according to a regular or periodic schedule are
found within the crontab files. Commands that are to run once only are found within the at files. You submit crontab and at file entries
by using the crontab and at commands. Because the cron process exits only when killed or when the system stops, only one cron daemon
should exist on the system at any given time. Normally, you start the cron daemon from within a run command file.
During process initialization and when cron detects a change, it examines the crontab and at files. This strategy reduces the overhead of
checking for new or changed files at regularly scheduled intervals. The cron command creates a log of its activities. The cron daemon
must be started from the system startup scripts because it must begin execution without a login user ID set. The cron daemon starts each
job with the following process attributes stored with the job by the invoking process: Login user ID Effective and real user IDs Effective
and real group IDs Supplementary groups
It also establishes the following attributes from the authentication profile of the account associated with the login user ID of the invok-
ing process: Audit control and disposition masks Kernel authorizations
DIAGNOSTICS
The at and batch programs will refuse to accept jobs submitted from processes whose login user ID is different from the real user ID.
FILES
Specifies the command path. Main cron directory Directory containing the crontab files. List of allowed users. List of denied users His-
tory information for cron Queue description file for at, batch, and cron
RELATED INFORMATION
Commands: at(1), crontab(1), rc0(8), rc2(8), rc3(8)
Files: queuedefs(4) delim off
cron(8)