FW: OT: broken/useless ansi - console driver??

[Kenneth Brody]

Quoting Jean-Pierre A. Radley (Tue, 25 Oct 2005 12:44:06 -0400):
[...]
> Nothing is going to be 'fixed', and you do not need to use ps.
>
> If you want to place a new binary in place, first move the old one to a
> different name, then copy in the new program.  People currently running
> the old version will see no change, but subsequent calls for the program
> will get the new version.
>
> 	mv /path/to/running/program /path/to/running/program.O
> 	cp /path/of/new/program /path/to/running/program
> 	rm /path/to/running/program.O
>
> The old version is not actually unlinked until any running instance has
> concluded.

Why rename it before removing it?  Can't you simply do:

    rm /path/to/old/binary
    cp /path/to/new/binary /path/to/old/binary

Though I still don't understand allowing writes to an executing binary
rather than giving the "text file busy" error.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com