🚀 go-pugleaf

Juris wrote:

> Delete self - sample.

Yeah that's doing what we said you'd have to. It creates an external
process to delete itself then it closes itself down before the created
process gets around to attempting the delete.

It seems to be doing this through a slightly underhand method though.
It creates the process at a very low priority after boosting itself to
a very high priority. IOW it's setting up a critical race and heavily
biasing the race in favour of itself. Whether this bias is enough to
guarantee successful deletion or just make it very likely I don't know.

I think it would be better and simpler to avoid all the clever trickery
and just have an external process that is responsible for (re)launching
the one you want to delete.

This is actually a very well known and documented technique. The
application the user invokes is just a wrapper and it takes care of
launching the real application and waiting for it to exit. When the
real application exits it signals the wrapper what to do next.

This is used for the purpose you seem to need and also to relaunch
processes if/when they abend.

-- 
Andrue Cope [TeamB]
[Bicester, Uk]
http://info.borland.com/newsgroups/guide.html