I've made some progress on my own so far. The only problem is that I assume that each file is incremented by 50 (VF_50, VF_100, VF_150 etc.) but this may not always be the case. I'd like to make it more general. This is how it looks now.
Code:
i=50
for dir in VF_*
do
if [ -d "$VF_$i" ]; then
cd VF_$i
pwd
cp ../VF_$i_old/restrt.bin .
./oppre_cT_T < inp01_$i > out.dat &
wait $!
else
echo Directory VF_$i does not exist.
fi
let i=$i+50
cd ../
done
i want to run few c object files one after another in one command. Can i write a acript for that. I'm using Sun Solaris.
for example
./prog < input1 >output1 &
./prog <input2 >output2 &
i want the first to finish before starting the nest one and run them in the back ground
thanks.... (5 Replies)
Hello script experts,
I am newbie to shell script. But I have to write a shell script (ASAP) where I need to ftp a file on daily basis to a remote server, and send an email with final status. I I should have a properties file with hostname, Userid, and pwd. And a shall script file should read... (1 Reply)
I am trying to automate a process (on windows OS) of manipulating a file by changing its column delimiters. I have a perl script ready but the problem i think is with the format of the file itself.
code:
#! usr/bin/perl -w
foreach (<STDIN>) {
#copy this line:
my $line = $_;
... (1 Reply)
I am a new member of this forum and am also new to unix shell scripting.
I joined the forum to seek for help to achieve my task as this forum helps people.
here's what i do manually on daily basis
1)Loginto different unix box
2)Ftp the log files (morethan 50 each dir) to windows
3)use text pad... (3 Replies)
Hi,
I'm trying to write a script to decompress a directory full of files. The decompression commands can run in the background, so that many can run at once. But I want to limit the number running at any one time, so that I don't overload the machine.
Something like this:
n=0
for i in *.gz... (15 Replies)
CAN ANYONE HELP TO SOLVE
i wann write a script to automate a process .i.e, to search files in the FTP server and
and if files are there and we hav to bring that files to our system.
After copying the files in our system we have to upload the data in the tables.
I have scripts to load the... (0 Replies)
Plzz Some One Help in this matter
I have scripts to load the data into tables and to copy files from ftp to our system.
we use to run the scripts every day....
we hav the files in the FTP server and we hav to bring the files to our system and we hav to load the data into the tables.
We... (0 Replies)
CAN ANYONE HELP TO SOLVE
i wann write a script to automate a process .i.e, to search files in the FTP server and
and if files are there and we hav to bring that files to our system.
After copying the files in our system we have to upload the data in the tables.
I have scripts to load the... (2 Replies)
Hi, guys, I am trying to automate a sftp process using "expect" method (since the key authentication method is disabled in my company network, there is no helping it).
In order to try, I type in the command manually:
sftp @ > << EOF
>cd
>ls -l
>EOF
>Connecting to
@servername password:
... (3 Replies)
Hello All!
First post...
I am working on a script that is used to recover a crashed drive from an rsync backup.
I'm down to the place where I need to create all of the directories in /mnt where I will then mount each of the volumes and begin the restore process to each volume...
I have... (3 Replies)
Discussion started by: RogerBaran
3 Replies
LEARN ABOUT OPENSOLARIS
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.11 1 Mar 1994 queuedefs(4)