08-18-2008
There are probably reasons they disabled cron, so workarounds are somewhat likely to be shut down for the same reasons. But anyway, you could run a background script which just stays dormant and wakes up at predetermined times to start up child processes, i.e. your own little cron daemon. Or if you have ssh login access, run a script on another machine's crontab which logs in over the network and runs the commands you want.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
We have three shell script batch, which extract data from three different systems(oracle, db2, db2/400).
By running each shell script batch, the data is extracted from respective systems. while the batch is running, job date, system_name, start_date and end_date will be inserted into... (1 Reply)
Discussion started by: anwarsait
1 Replies
2. Shell Programming and Scripting
Hi all I have a requirement where I have a flow like
Script1
script2 Script3 Script 4 Script 5 Script 6
script7
where script2 to script6 will... (3 Replies)
Discussion started by: nvuradi
3 Replies
3. Shell Programming and Scripting
Hi All,
Am using the below command to start my application using the root user
su - bin -c "/home/bin/test/start.sh"
but am getting the error becaue i have set some environment varibales in bin .profile
when i execute the command start.sh by logging directly into bin account it's... (8 Replies)
Discussion started by: ravi.sri24
8 Replies
4. Shell Programming and Scripting
Hi all,
I have set up a cron job which calls another shell script shell script which in turn calls a Java process. The cron tab looks so.
0,30 7-18 * * 1-5 /u01/home/weblogic/brp/bin/checkstatus.sh >> /u01/home/weblogic/logs/checkstatus.log
The checkstatus.sh scripts looks like this.
... (4 Replies)
Discussion started by: sirbrian
4 Replies
5. Shell Programming and Scripting
I would like to run two scripts using cron one immediately after the other. Is it enough to put them one after another in the cron file to run at the same time, or will this cause them to run concurrently? (4 Replies)
Discussion started by: 3210
4 Replies
6. Shell Programming and Scripting
Hi,
I am new to use minicom. I want script to run on minicom with username and password as automated.(Expect). please could anyone suggest the sample code for it.
Thanks in advance (2 Replies)
Discussion started by: vanid
2 Replies
7. Solaris
I need to run a script (from cron) that runs a second script.
What worries me is that second script, when run from bash, upon finishing doesn't return to bash unless I press the 'Enter' key.
I presume that's because last command in that script ends with &
Could that be a problem for cron?... (2 Replies)
Discussion started by: orange47
2 Replies
8. Shell Programming and Scripting
I am writing a bash script to run test some scripts.
The names scripts of the scripts to tests are stored in an array.
scptArr='chcksfrd.bash'
scptArr='compute-misfit.bash'
scptArr='compute-travel-times.bash'
scptArr='create-data-tinv.bash'
scptArr='create-docs.bash' ... (3 Replies)
Discussion started by: kristinu
3 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I need a script (ksh) on ServerAdmin that will run an archive scripts from different several Servers through ssh. The problem is that how can i switch user when before running the archive script. I already configured password-less connection on the servers.
server 1... (1 Reply)
Discussion started by: chococrunch6
1 Replies
10. UNIX for Beginners Questions & Answers
So I've written my first bash script.I wanted to run it from the command line, but I got an error:
$ myscript.sh
myscript.sh: command not found
So instead I try this and it works:
$ ./myscript.sh
Is this how I will always need to execute it? How can I run myscript.sh without having to... (2 Replies)
Discussion started by: P.K
2 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility 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).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not
be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO
crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)
AUTHORS
Paul Vixie <paul@vix.com>
BSD
June 17, 2007 BSD