9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] AFS-client for Plan9 - ?
Date: Wed, 15 Nov 2000 08:10:15 +0000	[thread overview]
Message-ID: <E13vxdh-000JOA-0C@finch-post-12.mail.demon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

Let me explain (and, yes, this is a quote from Fawlty Towers)

Programs which do not explicitly close flies before invoking exit() are
not

1) badly written

or

2) forcing Unix implementations to have to do close on exit to compensate

These are the defined semantics. So the reason is "because that's what
the program quite reasonably expects".

Just in the same way that you don't have to free all memory before
calling exit, unless, as in td's words "they've changed that since I
last looked".  I know "they" did for 16 bit Windows applications, and
it's certainly the case for semaphores in Unix.

> Grr... OK, let me rephrase it:
> 
> 	I really doubt that there is (or ever was) a UNIX variant that
> would not do close-on-exit. Reason: lots and lots of programs that would
> kill such system with file leaks.


[-- Attachment #2: Type: message/rfc822, Size: 2202 bytes --]

From: Alexander Viro <viro@math.psu.edu>
To: Tom Duff <td@pixar.com>
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] AFS-client for Plan9 - ?
Date: Tue, 14 Nov 2000 19:31:13 -0500 (EST)
Message-ID: <Pine.GSO.4.21.0011141923210.5482-100000@weyl.math.psu.edu>



On Tue, 14 Nov 2000, Tom Duff wrote:

> > Precisely. And any kernel that will try _not_ to do that will die under the
> > leaks produced by the $BIGNUM of applications expecting it do act as any
> > sane UNIX should.
> Which UNIX version lacks this behavior?
> (Or are you trying to run UNIX programs
> on some non-UNIX?)

Grr... OK, let me rephrase it:

	I really doubt that there is (or ever was) a UNIX variant that
would not do close-on-exit. Reason: lots and lots of programs that would
kill such system with file leaks.

IOW, "not likely" was about "some numskull changed it" part - such attempt
would backfire immediately. We are in violent agreement...

             reply	other threads:[~2000-11-15  8:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15  8:10 nigel [this message]
2000-11-15  8:20 ` Alexander Viro
  -- strict thread matches above, loose matches on Subject: below --
2000-11-20 15:25 rog
2000-11-21 16:04 ` Douglas A. Gwyn
2000-11-14 23:57 David Gordon Hogan
2000-11-13 20:22 presotto
2000-11-13 20:19 anothy
2000-11-14  9:58 ` Wladimir Mutel
     [not found]   ` <mwg@alkar.net>
2000-11-14 22:33     ` Tom Duff
2000-11-14 22:41       ` Boyd Roberts
2000-11-14 22:41       ` Alexander Viro
2000-11-14 22:51         ` Boyd Roberts
     [not found]           ` <boyd@planete.net>
2000-11-14 23:02             ` Tom Duff
2000-11-20 10:55           ` Chris Locke
2000-11-20 10:56           ` Douglas A. Gwyn
2000-11-20 13:24             ` Boyd Roberts
     [not found]         ` <viro@math.psu.edu>
2000-11-14 23:00           ` Tom Duff
2000-11-14 23:15             ` Alexander Viro
2000-11-14 23:54           ` Tom Duff
2000-11-15  0:31             ` Alexander Viro
2000-11-15  0:38               ` Boyd Roberts
     [not found] <200011131639.eADGdhI37677@smtp3.alkar.net>
2000-11-13 17:03 ` Wladimir Mutel
2000-11-13 16:39 presotto
2000-11-14 15:20 ` Boyd Roberts
2000-11-13 16:30 Wladimir Mutel

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=E13vxdh-000JOA-0C@finch-post-12.mail.demon.net \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /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).