Continuing on my script to automatically copy some huge files across the network onto various servers as background jobs, I need to be able to check that each job has finished successfully.
The script below shows what I want - almost. The problem is that some processes may obviously finish sooner than others, even though they were started afterwards. But the way the script is written it will do the first one, and when that's completed check the second one (which may already be done).
What I need is a way of getting the wait and exit code parts to also run as background jobs so they will finish as soon as the process has - but I'll be darned if I can work out how that would be written. I'm sure it'll be simple, but my brain is fried!
Anyone got any ideas? Thanks in advance.
Code:
set -A processvar
countervar=1
while [[ $countervar -le 4 ]]
do
seconds=$(( (RANDOM%60+1) ))
echo $seconds
sleep $seconds &
processvar[$countervar]=$!
(( countervar=countervar+1 ))
done
countervar=1
while [[ $countervar -le 4 ]]
do
wait ${processvar[$countervar]} ; echo Exitstate = $?
(( countervar=countervar+1 ))
done
Hello all,
How do I start a background process and save the process id to a file on my system. For example %wait 5 & will execute and print the process id. I can't figure out how to get it to a file. I've tried: > filename 0>filename 1>filename.
Any assistance is most appreciated.
Thanks,
Jim... (10 Replies)
Hello,
This has probably been answered in other forms, however I would like to confirm this statement before I use it in production. Will this syntax work for a background process?
echo "nohup server_process1 >/dir1/nohup.server_process1 2>&1 &" | ksh
Please advise. Thanks (1 Reply)
Hi
When I run ./script.sh &
the script runs in bg
But when I close the telnet session, the script is killed also.
any idea how to keep this script running?
thx (4 Replies)
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
Hello,
The scenario is as follows, I have a background process running initially for which i know the PID on machine1. I use ssh from machine 2 to execute a script in machine 1. For some reason the back ground process is terminated. I would like to know which process caused the ... (1 Reply)
Hello,
The scenario is as follows, I have a background process running initially for which i know the PID on machine1. I use ssh from machine 2 to execute a script in machine 1. For some reason the back ground process is terminated. I would like to know which process caused the... (6 Replies)
Hi,
I am using net::ftp for transferring files now i am trying in the same Linux server as a result ftp is very fast but if the server is other location (remote) then the file transferred will be time consuming.
So i want try putting FTP part as a background process. I am unaware how to do... (5 Replies)
Hi,
I have written a menu driven shell script in which as per the choice, I run the another script on background.
For eg:
1. get info
2)process info
3)modify info
All the operations have different scripts which i schedule in background using &.
However I wish to display the error... (0 Replies)
Discussion started by: ashima jain
0 Replies
LEARN ABOUT SUSE
ncftpbatch
ncftpbatch(1) General Commands Manual ncftpbatch(1)NAME
ncftpbatch - Individual batch FTP job processor
SYNOPSIS
ncftpbatch -d
ncftpbatch -l
ncftpbatch -D
OPTIONS
Command line flags:
-d Begin background processing of FTP jobs in the current user's $HOME/.ncftp/spool directory. This returns immediately, because a
daemon process is spawned and ran in the background.
-l Lists the contents of the user's job queue.
-D This is like -d, except that the process does not become a daemon.
DESCRIPTION
This program is responsible for processing background FTP requests. It is normally only run by ncftp and not manually by a human being,
however you can run it to manually process the FTP job queue.
The jobs are spool files written to a user's $HOME/.ncftp/spool directory and have a special format and file-naming convention (which con-
tains when the job is to be run). ncftp runs this program when it needs to, but if the ncftpbatch daemon dies unexpectedly the jobs that
are left in the queue will not be processed until another instance of ncftpbatch is run.
ncftpget and ncftpput can also be used to submit jobs for batch processing, using those utilities' -b command-line flag. If desired, you
can also manually create the spool files although this procedure is not documented here (see the manual page for ncftpspooler for more
information on how to do that).
DIAGNOSTICS
ncftpbatch writes to its own log file, the $HOME/.ncftp/spool/log file. This file should be examined to determine if any ncftpbatch pro-
cesses are actively working on jobs.
AUTHOR
Mike Gleason, NcFTP Software (http://www.ncftp.com).
SEE ALSO ncftp(1), ncftpput(1), ncftpget(1).
ncftpbatch NcFTP Software ncftpbatch(1)
11-11-2010
