this post was submitted on 09 Sep 2024
273 points (80.8% liked)
linuxmemes
20751 readers
446 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In Unix/Linux, a removed file only disappears when the last file descriptor to it is gone. As long as the file
/usr/bin/rm
is still opened by a process (and it is, because it is running) it will not actually be deleted from disk from the perspective of that process.This also why removing a log file that's actively being written to doesn't clear up filesystem space, and why it's more effective to truncate it instead. ( e.g. Run
> /var/log/myhugeactivelogfile.log
instead ofrm /var/log/myhugeactivelogfile.log
), or why Linux can upgrade a package that's currently running and the running process will just keep chugging along as the old version, until restarted.Sometimes you can even use this to recover an accidentally deleted file, if it's still held open in a process. You can go to
/proc/$PID/fd
, where$PID
is the process ID of the process holding the file open, and find all the file descriptors it has in use, and then copy the lost content from there.