The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: "Erik E. Fair" <fair-tuhs@netbsd.org>
Cc: tuhs main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] v7 /etc/ttys and /usr/adm/wtmp shenanigans
Date: Sat, 1 Jan 2022 13:36:52 +1000	[thread overview]
Message-ID: <CAKr6gn265xEXZY1biOQPQ+oco6VJ2MFi6CQNsrMUrPf25MxpSw@mail.gmail.com> (raw)
In-Reply-To: <28153.1641007110@cesium.clock.org>

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

It was bad luck if the process holding your file open was an unkillable
zombie. Reboot and clri fixes all things. Okay maybe "fix" isn't the word I
want...

On Sat, 1 Jan 2022, 1:27 pm Erik E. Fair, <fair-tuhs@netbsd.org> wrote:

> Classically, files don't get de-allocated (their blocks re-added to the
> filesystem free list) until the last open reference to their inode is
> removed, even if the file name is removed from all directories.
>
> This behavior is commonly used for temporary files: open(2) with O_CREAT
> and unlink(2), and file disappears when the file descriptor is finally
> closed or the process exits without explicitly closing the descriptor (the
> kernel will close all descriptors associated with an exiting process).
>
> Where process accounting is concerned, the kernel itself holds the inode
> reference until it is explictly told to turn off process accounting. See
> acct(2).
>
>         Erik Fair
>

[-- Attachment #2: Type: text/html, Size: 1276 bytes --]

      reply	other threads:[~2022-01-01  3:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 20:36 Will Senn
2022-01-01  2:46 ` Jacob Ritorto
2022-01-01  3:18   ` Erik E. Fair
2022-01-01  3:36     ` George Michaelson [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=CAKr6gn265xEXZY1biOQPQ+oco6VJ2MFi6CQNsrMUrPf25MxpSw@mail.gmail.com \
    --to=ggm@algebras.org \
    --cc=fair-tuhs@netbsd.org \
    --cc=tuhs@minnie.tuhs.org \
    --subject='Re: [TUHS] v7 /etc/ttys and /usr/adm/wtmp shenanigans' \
    /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

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).