Zsh Mailing List Archive
Messages sorted by:
Re: Waiting on Child
- X-seq: zsh-users 12875
- From: "Mikael Magnusson" <mikachu@xxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Waiting on Child
- Date: Wed, 28 May 2008 01:17:14 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=NQspngJzdv847bvjTA7FU1sXvQlGd4dmwma0nuTayv4=; b=aeVqHyIWplgTMV9qH6zarux/WNjuuMRJycDJziCTV/ALqt34xxjIUcCfWtE94cMEpTNSqAxP+DttX5eH8UrQ9Q73ImohiQQ4tyCbZUWGIvts5XejjlQB5D/hFBKNElLdXPSkSUPQSNoTFk3pSPd+U8C7L33zo92yDiemi/5g+N0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CDqy/5QF4roworh0J09HpUNrg2FeL4maR8P5fcjGEV6iSV81bJms3GCqmiAhaL7bMH+e87gApgY5tTXoNKtc/HnH6UfW7U3pK153HPe0Iai+Cm4OICMn3KAcoO7MYGc8u7sfdFltqWfZtYga908gjo/O0gz+kMQfnzicGB/lm88=
- In-reply-to: <20080527230328.GA25402@xxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20080527230328.GA25402@xxxxxxxxxxxxxxxxxx>
2008/5/28 Chris Johnson <cjohnson@xxxxxxxxxx>:
> I've got a script that opens in the foreground a file in OpenOffice.org.
> When the process ends, I do some other things to the file. This all
> worked great until I upgraded to OpenOffice 2.4. It seems now that a
> child process is spawned to deal with the document and the parent
> process does not wait for the child. The parent process ends and my
> script now incorrectly advances to the post-editing code.
> Is there anything zsh can do to help me? I want to be able to wait on
> the child process, but I don't think zsh can do anything about it.
> Probably I can twiddle with checking the output of ps, but ps-based
> scripts rarely seem portable.
> Any ideas? Thanks.
Looks like ooffice is communicating with an existing ooffice process
via the OSL_PIPE_* socket in /tmp, so I doubt there's anything you can
do to notice it closed the file... You could possibly use
inotifywait to watch for an appropriate event (i think
Messages sorted by: