Re^2: graceful handling of perl upgrades on server?

Aha -- that's good to know, thanks! Using lsof as you suggested, I notice that all my getty processes have a deleted version of libc open. Seems strange, since I'd think that that would have caused getty to crash, making it impossible for me to log in.

Comment on Re^2: graceful handling of perl upgrades on server?

Replies are listed 'Best First'.
Re^3: graceful handling of perl upgrades on server? by eye (Chaplain) on Dec 10, 2009 at 07:43 UTC
Deleting (unlinking) files doesn't make them go away. If something has the file open, it will prevent re-allocation of the files resources until the file is closed. libc should still be accessible to getty and any other application using it (including the OS). Note that an unlinked file cannot be closed and re-opened even within the same process.	[reply]