[Adium-devl] Let's abandon disk images
Ofri Wolfus
ofri.wolfus at gmail.com
Sat Mar 31 21:38:37 UTC 2007
I'm not really seeing the problem here.
1. Launch the copied app from /Applications.
2. fork/exec.
3. Parent calls exit() while the child does that system voodoo or
whatever, possibly prefixed by sleep() to make sure the parent
terminated.
Sounds reasonable (I have very little experience in this area)?
- Ofri
- - - - - - - - - - - - - - - - - - -
http://www.dpompa.com
- - - - - - - - - - - - - - - - - - -
On 01/04/2007, at 00:04, Graham Booker wrote:
> The advantage of the above script is that it waits for the existing
> app to quit before it does the relaunch, and so in theory, the disk
> image should no longer be in use. Although, I have issues with
> using system to launch an bash process which waits for the parent
> pid to exit. System launches sh with the argument passed into it,
> and blocks until the sh finishes. The sh then launches the bash
> process with the script in it in the background. The bash process
> waits in a loop for its parent to finish, which is the sh process,
> not the application itself. It seems to be sheer luck that the
> above works. I would prefer it to wait on a particular pid, which
> the application gives it, but that is just me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070401/e5791e4e/attachment-0001.html>
More information about the devel
mailing list