11-08-2008
Many a times after reboot, machines have a problem with cron job.
Machine : Linux
Solutions:
This problem can be solved by editing, or removing then "reentering" the cronjobs again after Reboot using crontab -e.
or
I suppose you will be using crontab -e to edit the cron jobs.
You can use Cronnix to edit cron files. So whenever you restart your machine it will reenter all those jobs automatically.
or
After Reboot, if the cronjob is not running,
One can do
sudo /etc/init.d/cron restart
Logs can be seen in anyone of the two
/var/log/auth.log
/var/log/syslog.
Try this and let me know your observation.
Hope this will clear the problem.
10 More Discussions You Might Find Interesting
1. Linux
Hi all,
i have a script in /etc/init.d directory.
-rwxr-xr-x 1 root root 26 Mar 28 16:00 myscript
I need it to run when my linux reboots/startup. However is it not being executed. Do i need to put in in the rc.local directory? (1 Reply)
Discussion started by: new2ss
1 Replies
2. Solaris
Hi experts,
I want to set the crontab for my script which will run every 20 seconds
I think below could be the possible one-
*/3 * * * * /export/home/username/scripts/runing.sh
As my system(SOLARIS 9) is live- i am confused to implement before make sure !!!
I need... (4 Replies)
Discussion started by: thepurple
4 Replies
3. UNIX for Dummies Questions & Answers
A basic cron question and I hope I explain it enough.
If a person creates a file to use with cron and issues the followin command:
crontab
I understand this will set the cron entries to whatever is in . However, if we now edit the crontab with:
crontab -e
and save, how does cron... (3 Replies)
Discussion started by: niswonp
3 Replies
4. Solaris
hi all,
I'm working Solaris 5.10 (5.10 Generic_137137-09 sun4u sparc SUNW,SPARC-E nterprise)
Few days ago, my junior engineer made a mistake! He is execute shutdown command on the live server. He mis understand between live and test servers! :wall:
The live... (0 Replies)
Discussion started by: buyantugs
0 Replies
5. HP-UX
Hi All,
We are working on HP_UNIX.
I am facing a strange problem regarding crontab in our unix environment.Whenever a server reboot takes place on our server the old crontab gets reflected due to which several scripts which were earlier uncommented starts running causing a huge problem .Is... (6 Replies)
Discussion started by: ammbhhar
6 Replies
6. Shell Programming and Scripting
Hi friends,,,
I am running one server on Ubuntu 12.04 LTS 32-bit, some times my pc restarts automatically, with no reason, I have a script to start server which requires root password. in this directory
/myserver/start_server.sh
How can I do this ?
and some scripts I am having that I... (1 Reply)
Discussion started by: Akshay Hegde
1 Replies
7. Shell Programming and Scripting
Hello all,
I'm trying to write a script to gather and send data and it works just fine at the bash command line, but when executing from CRON, it does not run properly.
My scripting skills are pretty limited and there's probably a better way, but as I said it works at the command line, but... (12 Replies)
Discussion started by: rusman
12 Replies
8. Shell Programming and Scripting
Hello,
I'm trying to create a mechanism wherein a set of Production servers will email me the results of system checks like Uptime, NFS Mounts and a Process after every scheduled reboot.
For this, I figured I'd use the @reboot parameter that crond comes with.
I have added the below onliner... (3 Replies)
Discussion started by: pocodot
3 Replies
9. Shell Programming and Scripting
I'm trying to get a crontab to run, every Friday at 11am and the problem is that it isn't running at all.
0 11 * * 6 /Users/martinb/Documents/SYSADMIN/Regular-Scripts/Info-And-Backups.sh
Here's a link to a screenshot of my script (I've censored my email address).
Screen Shot 2017 11 03... (3 Replies)
Discussion started by: $shell_Learner
3 Replies
10. Shell Programming and Scripting
Hello Team .
I am working a health check script ( bash) to run on linux server ( RedHat) and requirements are
1. The o/p of script need to be send to two diff files . I am testing with tee command . But I am not successful yet , any recommendations if that is the right approach ?
2. The same... (2 Replies)
Discussion started by: Varja
2 Replies
LEARN ABOUT REDHAT
crontab
CRONTAB(1) 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
Crontab 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 though these are files in /var, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the 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.
If the -u option is given, it specifies 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(8) can confuse crontab and that if you are running
inside of su(8) you should always use the -u option for safety's sake.
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 -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 29 December 1993 CRONTAB(1)