03-30-2009
Cron Jobs Still Running In Backgound
Hi guys,
I've got a few cron jobs ... porblem is they are running as intended but some of them just tend to stay there in sleeping mode for quite some time ... sometimes even days ... for example when i run the ps command i can see that some are still there although the same script had run many more times after that particular day !!!
Any idea folks?!
Thanks in advance
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I'm new to cron and I would like to know if this cron entry looks right.
Every monday to friday, at 9:15 AM execute the script called done_att.sh
Every monday to friday, at 3:15 PM execute the script called start_att.sh
15 09 * * /u54/jobs/done_att.sh
45 15 * *... (1 Reply)
Discussion started by: ted
1 Replies
2. UNIX for Dummies Questions & Answers
I would like to add a job using cron. I have following questions
- cron jobs are launched using what login-id
e.g. is the script launced using my login-id
- In which directory would the cron jobs be launched ?
- where do the environment variables required in the script being lauched come... (3 Replies)
Discussion started by: sharanbr
3 Replies
3. UNIX for Dummies Questions & Answers
I have some cron jobs that are taking a might long time. That is because they are screen scrapers and I inserted an extra long pause (10 minutes between screens) to be extra polite and minimize network traffic. I was going to have them run once a day but now I'm thinking once a week.
How do I... (2 Replies)
Discussion started by: siegfried
2 Replies
4. UNIX for Advanced & Expert Users
Before I get a million and one suggestions on all the things that could be wrong with my scripts - let me assure everyone that this is not the issue.
i have a RH EL ES4 server that stopped running all cron jobs except hourly, daily, weekly.
This has affected all users including root. No... (7 Replies)
Discussion started by: bill_k_Lopez
7 Replies
5. OS X (Apple)
I have a cron job set up to run a script on my Leopard Server every night. The job is set up as root, and when I run the script manually, it runs fine.
The problem is that it is not doing anything when it runs at night. In the cron log, it says it ran, but did not output the results to the file it... (3 Replies)
Discussion started by: yodomino6
3 Replies
6. Solaris
Hi,
I am logging into sun solaris unix box as asood user.Then sudo su_appssu
and scheduled my cron jobs.The user appssu is there In the /etc/cron.d/cron.allow . I do not understand why the jobs are not kicking by cron. Do I need to enter directly as appssu ?
Regards
Megh (10 Replies)
Discussion started by: megh
10 Replies
7. Shell Programming and Scripting
Hi
Is it possible to run different cron jobs at the same time? It appears that when I run ones at 15 min granularity that they may prevent ones running later in the day.
Should crons run at same time have impact on one another? (4 Replies)
Discussion started by: rob171171
4 Replies
8. Red Hat
Hi unix.com,
I'm currently experiencing a problem on one of our servers at work where between the hours of approx. 1:00 AM and 2:0 AM no jobs scheduled through cron run.
Now, in the cron logs I do see that all jobs are launched and I'm not seeing any errors anywhere - but - none of the jobs... (2 Replies)
Discussion started by: tunachamp
2 Replies
9. Red Hat
I've scheduled few jobs using cron. But they are not running .....
What might be the possible reasons ?? Also tell me how to troubleshoot.............
Please help me .......
Thanks in Advance. (2 Replies)
Discussion started by: vamshigvk475
2 Replies
10. UNIX for Beginners Questions & Answers
on linux redhat, ubuntu systems, what reason would there be for a cron job not running at exactly the time it was scheduled to run, everytime?
meaning, if i put something in cron to run every 120 seconds (2 minutes), why is it that some times, i find that cron would sometimes run the job a few... (1 Reply)
Discussion started by: SkySmart
1 Replies
LEARN ABOUT DEBIAN
faxcron
FAXCRON(8) System Manager's Manual FAXCRON(8)
NAME
faxcron - HylaFAX routine maintenance script
SYNOPSIS
/usr/sbin/faxcron [ -n ] [ -l lastrun ]
DESCRIPTION
faxcron is a command script that does routine upkeep tasks in a HylaFAX spooling directory hierarchy. This script is intended to be
invoked from cron(8) on behalf of the fax user (often the ``fax'' user is uucp) once a day, with the standard output sent by mail to the
HylaFAX administrator. For example, the following crontab might be set up for the fax user:
25 23 * * * sh /usr/sbin/faxcron | mail FaxMaster
The faxcron script does the following work:
o report statistics for facsimile transmitted since the last time faxcron was run.
o report statistics for facsimile transmitted in the past week.
o report statistics for facsimile received since the last time faxcron was run.
o report statistics for facsimile received in the past week.
o report any recent calls that failed suspiciously and return the associated trace log;
o purge data that is 30 days or older from the remote machine information directory;
o delete information that is 30 days or older from session trace log files;
o remove files from the tmp directory that are older than 1 day;
o remove files in the received facsimile queue that are 7 days or older;
o report sites that are currently having jobs rejected; and
o force all session log files to be owned by the fax user and kept with protection mode 644.
OPTIONS
-n Forces faxcron to run without updating any files.
-l lastrun
Forces the notion of the last time that faxcron was run to be lastrun. The value of lastrun is a date and time string of the
form ``MM/DD/YY HH:MM'' (the date(1) format string ``%D %H:%M'').
-info n Set the expiration time for data in the info database to be n days.
-log n Set the expiration time for session log data to be n days.
-rcv n Set the expiration time for files in the received facsimile queue to be n days.
-tmp n Set the expiration time for files in the tmp directory to be n days.
-mode m Set the file protection mode for session logs to m (a command line argument to chmod(1)).
NOTES
This script requires nawk(1) or gawk(1) and a date (1) program that supports the ``+format'' option.
If session logs are to be kept private this script must be modified to filter out sensitive information such as calling card numbers. (It
should also be run with ``-mode 0600'' so that session log files are not publicly readable.)
FILES
/var/spool/hylafax spooling area
/var/spool/hylafax/status/lastrun timestamp of last run
/usr/sbin/xferfaxstats for generating transmit statistics
/usr/sbin/recvstats for generating receive statistics
/var/spool/hylafax/tmp/faxcronXXXX temporary file for truncating session logs
/var/spool/hylafax/tmp/faxlogXXXX temporary file for logs of failed calls
SEE ALSO
cron(8), faxq(8), faxgetty(8), faxsend(8), xferfaxstats(8), recvstats(8), hylafax-server(5)
May 12, 1996 FAXCRON(8)