>When you unlink a binary that is being executed (for instance: >/bin/busybox), said binary is not deleted at once, because it is still >in use (processes executing it have a fd open on it). The binary is >just marked for deletion; when all processes executing it have exited, >the real deletion occurs.
One system I used, DNIX, would push an unlinked executing binary into swap space, then do the FS deletion. Was actually pretty nice, it 'just worked'. Once the last executing process died the swap space was released. There was very little extra kernel code involved, it just exploited existing mechanisms. I'm surprised that Linux doesn't do this, actually. -- Jim _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
