04-29-2015
That depends heavily on how you define "same time". If in above you run the remote command in background, you'll achieve a start of all scripts within a few seconds, as each ssh returns immediately after submitting the respective script. If that is not acceptable, you might consider using a cron job on each server, having synchronized the servers' clocks meticulously. But this would still carry a few seconds risk...
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
I have some script that run some commands and send results to my email. I want to run same script on mulitiple servers. How can I do that. I know there is an option "ssh". But I'm not quite sure how to use it in the script.
And also. scripts has some parameters like following,
if :... (10 Replies)
Discussion started by: s_linux
10 Replies
2. Shell Programming and Scripting
We have number of servers which belongs to platforms Solaris, AIX,HP-UX and LINUX. Monitoring tool 'Patrol Agent' process run on the servers to check for the server health and communicate with the Patrol server through the port 5181. During scheduled reboot and maintenance of servers we do receive... (1 Reply)
Discussion started by: subharai
1 Replies
3. Shell Programming and Scripting
Shell script to find the run time based on log entries?
Below is the log files content updated when the script test.sh runs. I would like to calculte the difference between first update time stamp and last update time stamp to find the run time of the script. The below log file shows the first... (1 Reply)
Discussion started by: mailtopranesh
1 Replies
4. Shell Programming and Scripting
Hi all,
I am a newbie.....am jus trying to connect to oracle thro a script, but not thro giving the username/password@server_name directly like
`$ORACLE_HOME/bin/sqlplus username/password@server_name
In the above line, once it is connected to Oracle, it shud ask me the username and password... (4 Replies)
Discussion started by: kritibalu
4 Replies
5. Shell Programming and Scripting
Hello Everyone,
How do we run vi/vim encrypted shell script without decryption on multiple servers. It is a simple bash script and vim -nx <filename> has been used to encrypt with desired password. Now I have few errors, the syntax is absolutely fine as I have run that script multiple times on... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies
6. Shell Programming and Scripting
Hi all,
I have a task for which I need to run some commands on one server1 and then jump from the server1 (using ssh and asking user to enter login credentials manually for server2 server) to server2 and run some commands there and exit.
I know the script I need here but problem is when I... (5 Replies)
Discussion started by: pat_pramod
5 Replies
7. Shell Programming and Scripting
hi,
how can i pass a password automatically when a shell script is running.
i have shell script(runscript.sh) which call another shell script inside it as a different user.
runscript.sh contains
su - nemo -c "/bin/main_script.sh"
but when i execute "runscript.sh" it try to run... (7 Replies)
Discussion started by: Little
7 Replies
8. Shell Programming and Scripting
I need to run a script on a bunch of remote servers. how can this be done without ssh into each individual server and run it
its under /sbin/script.sh on each server (1 Reply)
Discussion started by: tdubb123
1 Replies
9. Shell Programming and Scripting
I have bash shell script which is internally calling python script.I would like to know how long python is taking to execute.I am not allowed to do changes in python script.Please note i need to know execution time of python script which is getting executed inside shell .I need to store execution... (2 Replies)
Discussion started by: Adfire
2 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
Would like to write a Script which will run between 11am to 3 pm and send the results to output.txt.
Please suggest. (2 Replies)
Discussion started by: vasuvv
2 Replies
LEARN ABOUT PLAN9
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)