01-12-2007
Hi skybird666, yogiB's problem is not how to keep a program executed at the prompt running after logging off. The problem was with cron and I am stumped with the solution.
I haven't seen cron give problems like this. We have housekeeping jobs and such defined in cron for several users that aren't in the sys group and there is no such problem...
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am a total newbie to all things Unix. I've worked out I need to set up something that will allow me to automatically backup a DB for me, the DB is for a foum system I run.
Now, I've only found out I need to use telnet for this, and worked out hwo to log into telnet today. From here... (4 Replies)
Discussion started by: eludlow
4 Replies
2. Solaris
I'm trying to run cron jobs to start any inhibited processes after a system reboot.
I can schedule th cron, but i'm confused as to how to incorporated the reboot, since reboot is scheduled at different times, once every month.
How can I write this to start every 15 min after after a reboot
... (2 Replies)
Discussion started by: Remi
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
We have a group of hosts using which the cron jobs are submitted...
Few days ago i had submitted a cron job in of these hosts, but unfortunately forgot the host name :(
Can anyone please help me out in finding this host name from which the cron s submitting the job, i dont want the... (2 Replies)
Discussion started by: bhavanisree
2 Replies
4. UNIX for Dummies Questions & Answers
Despite my best efforts, my media streaming server still dies sometimes and I am in a random place trying to ssh into the server to restart it on my cell phone after customers start calling.... I tried using google to track down a script that would do the following
Every 5 min execute:
sudo... (1 Reply)
Discussion started by: ajhalls
1 Replies
5. Shell Programming and Scripting
Hi,
please help on this am trying to exec the below mentioned cron jobs
but its getting failed fro the past two days
###but when am trying to execte the cron by the times
23,29 18 * * * /export/home/inrvgo/thelak/China.sh
its getting exec properly
please help on this
#... (8 Replies)
Discussion started by: thelakbe
8 Replies
6. Solaris
Hello guys, I have one script running that I need to keep it running 24x7 so I'd like to know how can I implement a sort of monitoring process I mean if for some reason this process dies somehow it gets automatically started again.
Thanks. (8 Replies)
Discussion started by: cerioni
8 Replies
7. Solaris
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)
Discussion started by: jegaraman
2 Replies
8. Red Hat
I'm running cronjobs on a redhat 5.X. Cronjobs are getting failed frequently so how to find the root cause (2 Replies)
Discussion started by: karthik9358
2 Replies
9. Shell Programming and Scripting
Bonjour,
I have a large script with a lot of print statements and misc commands. Standard and error outputs are redirected like into the following code :
#!/usr/bin/ksh
LOG=/<some dir>/log
> $LOG
exec >>${LOG} 2>>${LOG}
print aaaaa
print bbbbb
print ccccc
...
some_cmd
That way,... (5 Replies)
Discussion started by: Fundix
5 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE
queuedefs(4)