02-14-2013
Quote:
Originally Posted by
lurkerro
I tried exactly the code you provided, and it starts 5 parallel processes but, after a short while it will start ALL the rest
(luckily I tested with small number of files)
Hm, I wrote it off the cuff, will check.
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
In a korn shell script, how can I run several processes in parallel at the same time?
For example, I have 3 processes say p1, p2, p3
if I call them as
p1.ksh
p2.ksh
p3.ksh
they will run after one process finishes. But I want to run them in parallel and want to display "Process p1... (3 Replies)
Discussion started by: sbasak
3 Replies
2. Shell Programming and Scripting
Hello,
I need to trim zeros from left side:
#echo $var1
00023456
But number of zeros is not constant.
How do I do that ?
thanks
Vilius (4 Replies)
Discussion started by: vilius
4 Replies
3. Shell Programming and Scripting
Hi,
I have a generic FTP script which will be called by 28 different processes in parallel (through a GUI tool) may or may not be at the exact moment (there could be a delay of about a minute or so).
./FTP.ksh 1 (1 through 28)
This script after importing file from remote m/c... (1 Reply)
Discussion started by: dips_ag
1 Replies
4. Shell Programming and Scripting
QUESTION: How do I run processes in parallel, so that the counter (in counter.txt) would vary in value (instead of just "0" and "1")? That is, how to not sequentially run inc.sh and dec.sh?
The shared counter (a single number starting as 0) is in a file counter.txt.
counter.sh is (supposed to... (2 Replies)
Discussion started by: courteous
2 Replies
5. Shell Programming and Scripting
Hi,
I have a shell script that creates 2 parallel processes. When I press ctrl+c, i want the parallel process to get killed as well.
#!/bin/bash
cmd1="script1.py"
cmd2="script2.py"
${cmd1} &
pid1=$!
echo ${pid1}
${cmd2} &
pid2=$! (7 Replies)
Discussion started by: sana.usha
7 Replies
6. Shell Programming and Scripting
I am writing a script to kick off a process to gather logs on multiple nodes in parallel using "&". These processes create individual log files. Which I would like to filter and convert in CSV format after they are complete. I am facing following issues:
1. Monitor all Processes parallelly.... (5 Replies)
Discussion started by: shunya
5 Replies
7. Shell Programming and Scripting
Hello all,
I tried to parralise my treatments but after a while 'ps -ef' display all child process <defunct> (zombie)
Parent bash script to process all files (>100000) in directory:
for filename in /Data/*.txt; do
./child_pprocess.sh $filename &
done
exit(0)I understand that the... (1 Reply)
Discussion started by: namnetes
1 Replies
TP(5) File Formats Manual TP(5)
NAME
tp - DEC/mag tape formats
DESCRIPTION
Tp dumps files to and extracts files from DECtape and magtape. The formats of these tapes are the same except that magtapes have larger
directories.
Block zero contains a copy of a stand-alone bootstrap program. See reboot(8).
Blocks 1 through 24 for DECtape (1 through 62 for magtape) contain a directory of the tape. There are 192 (resp. 496) entries in the
directory; 8 entries per block; 64 bytes per entry. Each entry has the following format:
struct {
char pathname[32];
unsigned short mode;
char uid;
char gid;
char unused1;
char size[3];
long modtime;
unsigned short tapeaddr;
char unused2[16];
unsigned short checksum;
};
The path name entry is the path name of the file when put on the tape. If the pathname starts with a zero word, the entry is empty. It is
at most 32 bytes long and ends in a null byte. Mode, uid, gid, size and time modified are the same as described under i-nodes (see file
system fs(5)). The tape address is the tape block number of the start of the contents of the file. Every file starts on a block boundary.
The file occupies (size+511)/512 blocks of continuous tape. The checksum entry has a value such that the sum of the 32 words of the direc-
tory entry is zero.
Blocks above 25 (resp. 63) are available for file storage.
A fake entry has a size of zero.
SEE ALSO
fs(5), tp(1)
BUGS
The pathname, uid, gid, and size fields are too small.
7th Edition May 15, 1985 TP(5)