Quote:
Originally Posted by Perderabo
Well then blowtorch could open the executable for writing and truncate it to zero bytes. That would not be "storing data".
Oh yeah, I tried this. It dies with a bus error and a dumped core. This shouldn't be happening. If Solaris is going to open a running executable for writing, then it should be able to truncate it as well. If it has to be consistent, it should either allow me to carry out any write related operation, or it should prevent me from performing any write related operation.
-Edit
I just tested this on FreeBSD (I use m-net.arbornet.org for this), and the unlink shown by Vino works, but my attempt to open the file for writing doesn't.