From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: executable ELF is rm-ed from disk, but still running RAM..
Date: Tue, 31 May 2011 13:53:13 +0700 [thread overview]
Message-ID: <BANLkTi=5gKy1-t=bJ5ZOr_LFtp+23nBteg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikav59rChzB=wirvMH_7NT34yf3OQ@mail.gmail.com>
On Tue, May 31, 2011 at 11:56, Vikash Kumar <vikashskumar@gmail.com> wrote:
> AFAIK Linux removes the directory entry and reduces the reference count of
> Inode of a running process and rm is successful. So, you can't see it in the
> file system anymore. However as the program is still running the inode
> reference count is still not zero and so the Inode and hence file is
> actually not deleted yet. When the program will terminate, Inode ref count
> will drop to zero and in that case the Inode and file will be freed.
> "The design of Unix Operating System" by Maurice J. Bach It covers these
> basic design principles in good detail.
Thanks people...you put valuable feedback to me. It's good to see I am
around knowledgeable people :)
As for the deletion case, I might do further research to see how the
very recent Linux kernel behaves. Hopefully, if the time permits...
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-05-31 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 14:49 executable ELF is rm-ed from disk, but still running RAM Mulyadi Santosa
2011-05-30 16:26 ` Jonathan Neuschäfer
2011-05-31 1:25 ` Pei Lin
2011-05-31 2:46 ` Mulyadi Santosa
2011-05-31 2:57 ` Manish Katiyar
2011-05-31 3:45 ` Mulyadi Santosa
2011-05-31 4:42 ` Manish Katiyar
2011-05-31 4:56 ` Vikash Kumar
2011-05-31 6:53 ` Mulyadi Santosa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=5gKy1-t=bJ5ZOr_LFtp+23nBteg@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).