All of lore.kernel.org
 help / color / mirror / Atom feed
From: jlnance@unity.ncsu.edu
To: Shriram R <shriram1976@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Effect of deleting executables of running programs
Date: Mon, 23 Aug 2004 09:30:00 -0400	[thread overview]
Message-ID: <20040823133000.GA4395@ncsu.edu> (raw)
In-Reply-To: <20040818181646.28610.qmail@web11412.mail.yahoo.com>

On Wed, Aug 18, 2004 at 11:16:46AM -0700, Shriram R wrote:
> a) I always thought that once a job is running, the
> executable is entirely loaded into memory and the
> abcd.out file is no longer needed.
> If so, then why does the a running job crash on
> deleting abcd.out ?  

No, programs sections are paged in as needed, so the
parts that are not running may not be in memory.

That said, the Unix way of dealing with files is by
reference counting.  This means that you can open a
file and delete it, and it is still kept around on
the disk until you close it (running a program counts
as having its file open).  So you are susposed to be
able to delete a program and running instances will not
be affected.

Unfortunatly, as you have discovered, NFS is kinda
sorta almost like a Unix file system, but not really.
You can NOT reliably access deleted files over NFS.
This is the root of what is causing your bus errors.

> b) To what extent can I trust that the rest of the 6-7
> jobs that are running have not been affected by this
> deletion of "abcd.out" ?

They are probably OK.

Thanks,

Jim

  parent reply	other threads:[~2004-08-23 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 18:16 Effect of deleting executables of running programs Shriram R
2004-08-18 19:18 ` Chris Wedgwood
2004-08-23 13:30 ` jlnance [this message]
     [not found] <200408181901.i7IJ1FK08538@orbit-fe.eng.netapp.com>
2004-08-18 20:11 ` Shriram R
2004-08-18 23:41   ` Ryan Cumming

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=20040823133000.GA4395@ncsu.edu \
    --to=jlnance@unity.ncsu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shriram1976@yahoo.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.