07-27-2011
hm, I have a feeling cron is better idea..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am having problems with a sparc5 solaris 7 box, when i try to edit cron, (crontab -e as root), it says
$ crontab -e
0
and then nothing, if i enter anything it errors out but does accept q for quit. But doesn't bring up my editor of the cron file. How can I troubleshoot this?
... (3 Replies)
Discussion started by: kymberm
3 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have put the following entry in crontab and it is NOT working
1 * * * * && /mybin/myjob.sh
As today is Sep 26th, Iam using NF-4 to test.
Thanks (2 Replies)
Discussion started by: baanprog
2 Replies
3. UNIX for Advanced & Expert Users
Dear all
We have SunOS 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V250
i have scheduled cronjob but its not working
Crontab details
15 15 * * * /d5/oratest/testdb/hotbackup_new.sh TEST247
15 15 * * * mkdir -p rajesh /d4/appltest
Crontab log details
> CMD: mkdir... (4 Replies)
Discussion started by: rajesh_hv
4 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I had setup crontab to execute my script every day midnight 00:00
Below are the current settings.
crontab -l
0 0 * * * /apps/bin/compress.ksh_moht > /dev/null 2>&1
Should it not work?
I need help fix this? (8 Replies)
Discussion started by: shifahim
8 Replies
5. Red Hat
I can run manually script of ntopdump.sh but crontab can't run this script very five minutes.
# crontab -l
*/3 * * * * root sh /root/ping.sh
*/5 * * * * root sh /root/ntopdump.sh
#
# pwd
/root
# ls -l
total 88
-rwxrwxr-x 1 root root 1645 Jun 14 19:01 anaconda-ks.cfg
drwxrwxr-x 2 root... (14 Replies)
Discussion started by: getrue
14 Replies
6. Solaris
Shell = ksh
Hi all,
I scheduled an automated job on my application server like below,
30 13 * * 1-5 $HOME/my_script.sh
However the script was not executed as expected. Any reason that may cause this to happen? (6 Replies)
Discussion started by: isaacniu
6 Replies
7. UNIX for Advanced & Expert Users
Hi,
When I set the crontab to run every minute, every hour, it works fine.
* * * * * env > /tmp/env.output
However I want to run it every day at 8:00 AM and it does not run.
* 8 * * * env > /tmp/env.output
I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (0 Replies)
Discussion started by: samantha13
0 Replies
8. Linux
Hi,
I know this is a common topic. I'm trying to launch a perl script using a contab -e entry. I've been trying diff options but nothing seems to work:
My cron is running:
UID PID PPID C STIME TTY TIME CMD
root 3755 1 0 Nov27 ? 00:00:00 crond
This... (4 Replies)
Discussion started by: krebe
4 Replies
9. Shell Programming and Scripting
Hi All,
I have a script with deatils as :
$ ls -ld catch_logs.sh
-rwx--x--x 1 muser muser 752 Jun 5 22:36 catch_logs.sh
User crontab looks likes:
$ crontab -l
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
* * * * * /opt/scripts/catch_logs.sh
Now if I run this script... (7 Replies)
Discussion started by: Junaid Subhani
7 Replies
10. Red Hat
Dear Friends,
I have Red Hat Linux Enterprise version 6.3. running SAP and oracle.
I have created one crontab for user orasid to execute one job periodically.
But it is not executing. I have checked crontab service is running.
Please help in the matter.
Regards,
Bhagawati Pandey (5 Replies)
Discussion started by: BPANDEY
5 Replies
LEARN ABOUT FREEBSD
atrun
ATRUN(8) BSD System Manager's Manual ATRUN(8)
NAME
atrun -- run jobs queued for later execution
SYNOPSIS
atrun [-l load_avg] [-d]
DESCRIPTION
Atrun runs jobs queued by at(1).
Root's crontab(5) file /etc/crontab has to contain the line
*/5 * * * * root /usr/libexec/atrun
so that atrun gets invoked every five minutes.
At every invocation, atrun will start all the jobs in the lowercase queues whose start time has elapsed. In addition, if the load average
over the last minute was less than the specified limit then a maximum of one batch job (denoted by the uppercase queues) is started.
Before starting a job, atrun will check the status of its owner's account with pam(3) and refuse to run the job if the account is unavail-
able, e.g., locked out or expired.
OPTIONS
-l load_avg
Specify a limiting load factor, over which batch jobs should not be run, instead of the default of 1.5 * number of active CPUs.
-d Debug; print error messages to standard error instead of using syslog(3).
WARNINGS
For atrun to work, you have to start up a cron(8) daemon.
FILES
/etc/pam.d/atrun pam.conf(5) configuration file for atrun
/var/at/jobs Directory containing job files
/var/at/spool Directory containing output spool files
SEE ALSO
at(1), crontab(1), pam(3), syslog(3), crontab(5), pam.conf(5), cron(8)
BUGS
The functionality of atrun should be merged into cron(8).
BSD
October 30, 2012 BSD