10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi I want to set up a cron for every 15 minutes between some hours.
Can you tell whether the below command will work.
Getting confuse because my time goes from night to next day morning.
i want to setup 8 PM to next day 10 AM.
*/15 20-10 * * * sh abc.sh (1 Reply)
Discussion started by: raju2016
1 Replies
2. UNIX for Dummies Questions & Answers
Good evening, ive got this cron to be run:
if i run this manually it doesnt work,it takes me to the prompt again
/export/app/CO/opge/scr/Informe_parametros_colombia.ksh >/dev/null 2>&1
here is the code fragment:
coopge@coopge: opge PRODUCCION>more... (1 Reply)
Discussion started by: alexcol
1 Replies
3. Shell Programming and Scripting
I am new to creating crontab file , i just wrote below
(40 19 * 3 * /root/maths/practisecron.sh), the script just prints "Hi".
When ever i save the above file i am getting this .
# crontab -e
crontab: installing new crontab
Can you please check where it went wrong.. (1 Reply)
Discussion started by: vkiyv05
1 Replies
4. UNIX for Dummies Questions & Answers
I am trying to setup a cron that runs a script to update my ip for my domain name every time I reboot and checks if my ip changes every 5 minutes and if it does then I update it. I am running Ubuntu server 12.04.
The file /etc/cron.d/ipupdate contains
#
#
# Run ipupdate
#
#
/5 * ... (3 Replies)
Discussion started by: Bros2
3 Replies
5. Ubuntu
Hi guys. This is my first post so bear with me.
I'm trying to get cron to run a shell script in my home directory (/home/server) that checks the temperature of my HDD. The script works fine, however I can't run it in cron. I've checked the syslog and I have only seen two errors:
- Exited with... (11 Replies)
Discussion started by: Rautoner
11 Replies
6. UNIX for Dummies Questions & Answers
Hi friends,
today i created a cron job , registered the crontab file associated but dont know why the cron is not getting executed at the right time.??
content of Crontab file :
21 15 * * * /subrat/myt
i wanted to execute the script myt on 15:21 PM of everyday.
the script myt... (2 Replies)
Discussion started by: paras.oriental
2 Replies
7. Programming
how to store a date into file?
and how we can access date from the file?
---------- Post updated at 06:09 AM ---------- Previous update was at 06:08 AM ----------
how we can store date in file? (1 Reply)
Discussion started by: causalmodi777
1 Replies
8. UNIX for Dummies Questions & Answers
Ok, so I have an nfs mount setup and within it there are symbolic links to other directories and such.
So anyways I created a link to a directory like so
ln -s /var/stuff/more/stuff/here/ stuff/
and i ended up with directory stuff with link 'here' inside.
so i was pieved and decided... (1 Reply)
Discussion started by: VRoemer
1 Replies
9. UNIX for Dummies Questions & Answers
Hi there,
this time a have a other problem :)
i will start a script over the cron.
if i start the script manual (per command) it works without any problems, but over the cron it doesent work.
my cron looks like this:
26 15 * * * /path/scriptname.sh 2> /path/error.log
there is no... (3 Replies)
Discussion started by: scotty
3 Replies
10. UNIX for Advanced & Expert Users
Hi, I am having a few problems with cron.
I have created a shell script (to rotate www logs - this works) and then did the following (as root)
#crontab -e
2 0 * * 3 /cron_scripts/wwwlogs.sh
?
w
?
q
#
crontab -l
entry not shown e.g. it did not show what I had just writern
I then... (6 Replies)
Discussion started by: warrend
6 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When
executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab,
if such exists).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time
has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD