I am running AIX 5.3 with the default shell as ksh.
I would like to know how to run a cron job on this system the last calendar day of the month. I found an example, but, I'm not sure if it will work with AIX and ksh...
I also need to be able to run a job on every day except the last calendar of the month (actually a series of jobs, but, I assume I can adopt the syntax for multiple jobs).
So to summarize:
I would like to run the following jobs where specified EXCEPT on the LAST calendar day of the month.
And I would like to run another job ON the LAST calendar day of the month, and probably a couple of others...
I'm also fairly new at shell scripting, etc., especially ksh.
Where can someone find info on Cron Jobs? Very new to UNIX and the PC I inherited looks to have several of them. Looks like they are some kind of background program that runs automatically at specified times. Would like to delete some of them and know more about them. (6 Replies)
Hi all,
Needs your help in scheduling a cron job for the below mentioned requirement. Just let me know if anybody has a similar job running as mentioned below:
Month end reports - Report of all items created in a parent table that were created during the week.
Presently this report runs... (3 Replies)
Hi,
How to get the lastmonth's end date? (have current date) through s shell script. I need to get it and pass it to a procedure.
Please advice.
Thanks in advance. (7 Replies)
There are two jobs in Solaris , Cron and at jobs..
I know how to disable or enable cron jobs.
How can I enable at jobs and disable it.
Kindly help.
Rj (2 Replies)
Hi pals,
Pls tel me how to cancel print jobs for an entire month (ex : sept)?
lpstat -oLBNDUIP061 | grep -i Sep is listing me hundreds of jobs.
Thanks in Advance,
Satish
Video tutorial on how to use code tags in The UNIX and Linux Forums. (22 Replies)
Hello,
I'm on FreeBSD 8.2-STABLE shell and I was trying the following cron entry for end of month:
59 23 * * * && /home/user/eomt.sh >/dev/null 2>&1
I get the following error
Subject: Cron <user@shell>
eomt.sh contains the following codes
#!/bin/sh
rm /home/user/tst/logs/* &&... (9 Replies)
How to see which cron jobs are not running? (2 Replies)
Discussion started by: rahul.raj1989
2 Replies
LEARN ABOUT SUNOS
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.10 1 Mar 1994 queuedefs(4)