9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello Team .
I am working a health check script ( bash) to run on linux server ( RedHat) and requirements are
1. The o/p of script need to be send to two diff files . I am testing with tee command . But I am not successful yet , any recommendations if that is the right approach ?
2. The same... (2 Replies)
Discussion started by: Varja
2. Shell Programming and Scripting
Hi ! all, I have once script to remove temporary cache and temporary xml files
looks like this, as it is taking more space, I would like to run automatically every 12 hour once, and then I want to receive some log as acknowledgement
echo "Removing logs and temp files (typically... (4 Replies)
Discussion started by: Akshay Hegde
3. Shell Programming and Scripting
I am running one server on Ubuntu 12.04 LTS 32-bit, some times my pc restarts automatically, with no reason, I have a script to start server which requires root password. in this directory
How can I do this ?
and some scripts I am having that I... (1 Reply)
Discussion started by: Akshay Hegde
Am new to AIX please help me. I have AIX7 server. When ever the system reboots my script need to run automatically. This will help me to start my application automatically after the server reboot.
Prince Wells (9 Replies)
Discussion started by: prince1987
5. Shell Programming and Scripting
I am using ksh as the shell. I have a script that should store variable after executing "onstat" on informix. I can execute it successfully without any issue if run manually, however the value is not showing up when run automatically(scheduled).
Is there anything needed to make the... (1 Reply)
Discussion started by: tungaw2004
6. Shell Programming and Scripting
How can i run a script every week automatically.
Thanks & regards,
Sam (5 Replies)
Discussion started by: sam25
7. Shell Programming and Scripting
I want to run/execute a bash script automatically everytime when a specific file is created or when its timestamp changes. Is this possible? How?
Thank you very much for your answers in advance,
Christoph (1 Reply)
Discussion started by: ckofler
8. Shell Programming and Scripting
i m trying to run bash scrip automaticially but i dont know how i can do this an anybody tell me how i can autorun shell script when i logon .
thanks (9 Replies)
Discussion started by: tahir23
9. UNIX for Dummies Questions & Answers
How to make a script run automatically using a cron??
i do not know abt cron......
if i have simple.sh file and i need this to run everyday at a particular time what needs to be done
thanks in advance (4 Replies)
Discussion started by: hamsa
queuedefs(4) File Formats queuedefs(4)
queuedefs - queue description file for at, batch, and cron
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:
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.
Example 1 A sample file.
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.
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.11 1 Mar 1994 queuedefs(4)