11-25-2011
Many things that do not work correctly in cron are due to misunderstanding of user:
cron is a dumb daemon that launches at the time stated the job asked, but it know nothing about the needed environment by default - Worse: It has no terminal attached..
So anything TERM / stty related will poduce error lines, the lack of environment settings also...
You mention nothing about the OS, nor what you call dependency... but a good start is to go and see what you have in your cron logs
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Im having this problem ever since im Using Unix. Please help.Im using Linux Red Hat 7.0. 2.2.6. My Problem is. Whenever i close my unix before the system goes to Halt mode and stoping all md device, this Process shows me as fail. :
Saving Mixer settings modprobe: modprobe: can't locate module... (1 Reply)
Discussion started by: killerserv
1 Replies
2. Programming
I have successfully opened /dev/table/proc file and read processes pids and its details from it, but I am unable to have programatic knowledge of how to access process CMD or its corresponding name.
Kindly do guide me out on the said request for which I will be very thankfull. (3 Replies)
Discussion started by: S.P.Prasad
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have this doubt....
When some program is running and if we press CTRL+Z...it is suspended...
what should we do to continue its execution
I know that KILL can be used to completely terminate the process....but is there any way to continue...
Thanks (3 Replies)
Discussion started by: proton
3 Replies
4. Programming
Hi,
i need to find the process name using the process id in C. This has to be done in HP, AIX, Solaris & Linux??
How can this be done? Is there any common solution to all platforms?
On linux i have heard that /proc/<pid>/cmdline can be used. Is there a structure available to read this?
... (3 Replies)
Discussion started by: molu
3 Replies
5. UNIX for Dummies Questions & Answers
Hi
does unix keep track of the processes or programs it ran. can i check when my program last ran on the system.
any suggestions are welocme.
-- logs made by the program it self are missing.
Regards
Debadatta (4 Replies)
Discussion started by: mishra.dd
4 Replies
6. Shell Programming and Scripting
What are some ways to tell if a given file is presently being used
by a process? How can you tell what sort of access the process has
to the file (read from, written to, filehandle held open, etc)?
Can more than one process access the file at the same time? (2 Replies)
Discussion started by: choco4202002
2 Replies
7. Shell Programming and Scripting
Hi,
We have UNIX menu.
when we exit the menu the processes are not getting log out.
please suggest me how to log out the process after exit from the UNIX Menu.
Regards,
laknar. (3 Replies)
Discussion started by: laknar
3 Replies
8. Shell Programming and Scripting
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies
9. Red Hat
Hi,
I'm running weblogic 11g on Linux platform. My requirement is to have weblogic instances running and it is controlled by Nodemanager. In the sense, when ever the weblogic instance goes down, Node manager should start it.
The set up requires to have weblogic running as user X, and... (2 Replies)
Discussion started by: aprasad
2 Replies
10. UNIX for Dummies Questions & Answers
I have to create a parent process that receives n arguments, arg1, arg2 ... argn. The parent creates n son processes. Each one of these will read a text file argi and will print the pair of lines from the file in reversed order.
Can anyone help me with this problem, please? (3 Replies)
Discussion started by: oana06
3 Replies
LEARN ABOUT POSIX
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)