From owner-freebsd-questions@FreeBSD.ORG Wed Nov 8 11:12:18 2006 Return-Path: X-Original-To: freebsd-questions@FreeBSD.org Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B04516A47C for ; Wed, 8 Nov 2006 11:12:18 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 811D343D5E for ; Wed, 8 Nov 2006 11:12:17 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 14372 invoked from network); 8 Nov 2006 22:12:16 +1100 Received: from 203-217-72-200.dyn.iinet.net.au (HELO localhost) (203.217.72.200) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Nov 2006 22:12:16 +1100 Date: Wed, 8 Nov 2006 22:12:12 +1100 From: Norberto Meijome To: nicky Message-ID: <20061108221212.430b2ec2@localhost> In-Reply-To: <4551B8D2.3020502@valuecare.nl> References: <4551AC4A.2000108@valuecare.nl> <4551B8D2.3020502@valuecare.nl> X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Andrew Pantyukhin , freebsd-questions@FreeBSD.org Subject: Re: Parallel shell scripts. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 11:12:18 -0000 On Wed, 08 Nov 2006 12:00:34 +0100 nicky wrote: > The whole idea is this. I have to extract two different databases to csv > files. One takes about an 1 hour, the other 1.5 hours. The problem is my > time window, which is 2 hours. So extracting one after the other is not > an option. After both extractions are complete, it should load the csv > files into a target database. Andrew has a point - I think you are going the *very* hard way around... an easier way , i think, may be : dump1.sh : handles extraction of first DB. Checks its own return status AND write to a tmp file flagging success or failure (i dont know, dump1.ok or dump1.bad... or different content which you can cat / grep for...) dump2.sh : same as dump1, with obvious differences. loader.sh : loops, check for both .ok flags , wait if not there yet and handle as it should. Launch a term, run screen (if running on a remote server..this would be a must, i think...) , launch dump1.sh, then from another session, dump2.sh . Or use cron if you dont like screen. and , of course, launch loop.sh to monitor them both... may have more components...but it's far easier to get it right, IMHO _________________________ {Beto|Norberto|Numard} Meijome "He uses statistics as a drunken man uses lamp-posts ... for support rather than illumination." Andrew Lang (1844-1912) I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.