04-10-2007
By concurrency, I assume you are referring to simultaneous execution of processes. Unless you are on a multi-processor system the real concurrent execution of any processes is not possible.
In your case, you could try something like,
split the files such that there are 10 10K files
run each of the script individually as a background process
<script> for the first file with 10K & ( in background mode)
run through the loop for all the files
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
OS - Sun OS7
What sources can I go to to figure out what is the maximun number of processes for OS7 with 2GB of memory.
I believe it is 64K processes, but this number reflects resources being swaped.
Any help is appreciated
SmartJuniorUnix (1 Reply)
Discussion started by: SmartJuniorUnix
1 Replies
2. UNIX for Dummies Questions & Answers
we've got solaris 5.6 installed in a ultra 5 box that serves as gateway server going to the main unix box.
just like to find out how to determine the number of concurrent terminal connections and processes that the ultra 5 box can handle? and handling at present time?
thanks in advance! (1 Reply)
Discussion started by: eddie_villarta
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
I notice in my Sun Solaris 8 sparc workstatin, I am able to login concurrently using a same user ID.
Is there a way to disallow this? That is, at anyone time, the user can have only 1 login session.
How can it be done?
Thanks (10 Replies)
Discussion started by: champion
10 Replies
4. Shell Programming and Scripting
Hi
I have a ksh that can have multiple instances running at the same time.
The script (each instance) uses the SAME log file to write to.
Should this cause a problem or is the ksh clever enough to queue write requests to the file?
Thanks.
GMMIKE (2 Replies)
Discussion started by: GNMIKE
2 Replies
5. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
6. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
7. AIX
Hi,
on normal (non concurrent) vgs, it's possible to extend a lun on san-storage , and use chvg -g to rewrite vgda, and use disks with the new size for lvm operations
is the same procedure possbile on a hacmp-cluster (2 node in our case) with concurrent vgs in active/passive mode?
cheers... (5 Replies)
Discussion started by: funksen
5 Replies
8. Shell Programming and Scripting
Hi all,
I have a folder with sql files that need to be inserted in a DB with SQL*Plus. The thing is that it takes too long to insert them all one by one, so I want to insert them five at a time.
Currently what I use is this:
for $FILENAME in *.sql
do
sqlplus -s $DBUSER@$SID << EOF
... (0 Replies)
Discussion started by: Tr0cken
0 Replies
9. Shell Programming and Scripting
Hi,
The problem detail is follows
I have three individual scripts .
SCRIPT A
sh -x sqoop_channels_nc_daily_01.sh & sh -x sqoop_channels_nc_daily_02.sh & sh -x sqoop_channels_nc_daily_03.sh
SCRIPT B
sh -x sqoop_contacts_nc_daily_01.sh & sh -x sqoop_contacts_nc_daily_02.sh & sh -x... (1 Reply)
Discussion started by: H_bansal
1 Replies
10. AIX
Hi,
What are the differences between concurrent and enhanced concurrent VGs.?
Any advantages of enhanced concurrent VG over normal concurrent vg
Regards,
Siva (2 Replies)
Discussion started by: ksgnathan
2 Replies
fsx(8) System Manager's Manual fsx(8)
NAME
fsx - file system exerciser
SYNOPSIS
/usr/field/fsx [-h] [-ofile] [-tn] [-fpath] [-pm]
OPTIONS
The fsx options are: Prints the help messages for the fsx command. Saves the output diagnostics in file. Run time in minutes (n). The
default is to run until the process receives a Ctrl/C or a kill -15 pid command. Number (m) of fsx processes to spawn. The maximum is 250;
the default is 20. Path name of directory on file system you wish to test. For example, /mnt or /usr. The default is /usr/field.
DESCRIPTION
The fsx exerciser spawns the background process fsxr, and these two processes exercise a file system by creating, opening, writing, open-
ing, reading, validating, closing, and unlinking a test file. These test files are created in the /usr/field directory (the default)
unless the -fpath option is used.
You can spawn up to 250 (default is 20) fsx processes (fsxr1, fsxr2, ... fsxrn where n is the number of processes spawned). The exerciser
will run until a Ctrl/C or kill -15 pid command is sent to the process.
A logfile for you to examine and then remove is created in the current working directory. If there are errors in the logfile, make sure you
check the syslog file where the driver and kernel error messages are saved.
RESTRICTIONS
If you must run a system exerciser over an NFS link or on a diskless system, there are some restrictions. For exercisers such as fsx(8),
which must write into a file system, the target file system must be writable by root. Also, the directory in which any of the exercisers
are executed must be writable by root because temporary files are written into the current directory. These latter restrictions are some-
times difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of the
restrictions may be overcome by copying fsx and fsxr to another directory and then executing it. Avoid using the fsx exerciser over an NFS
or diskless file system.
Each time you run fsx, it creates a log file. The exerciser allows you to accumulate up to 9 log files. If you run fsx to create a tenth
log file, it exits and displays the following error messages:
fsx: Remove old log files fsx: Can not start report generator, test aborted
When this situation occurs, remove at least one log file and run fsx again.
EXAMPLES
The following example runs 10 fsx processes on /mnt until the process receives a Ctrl/C or kill -15 pid command: % /usr/field/fsx -p10
-f/mnt The following example runs 20 fsx processes on /usr/field for 120 minutes in the background: % /usr/field/fsx -t120 &
SEE ALSO
Commands: cmx(8), diskx(8), memx(8), shmx(8), tapex(8)
fsx(8)