9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: [9fans] Re: patch/list sorry/proc-mtime
Date: Thu, 30 Mar 2006 01:07:30 +0200	[thread overview]
Message-ID: <790bcfc18f41984ae2b80dd2d05f94c3@cat-v.org> (raw)
In-Reply-To: <dfb566242e58a31d6d4f97b379b4f487@plan9.bell-labs.com>

> d-rwxrwxr-x M 430 uriel sys 0 Mar 29 17:43 sorry/proc-mtime
> from uriel@cat-v.org
> 	/sys/src/9/port/devproc.c
> 	Make the mtime for files under /proc be the creation time of the process rather than the boot time.
>
> Wed Mar 29 17:42:05 EST 2006 rsc
>     This is an interesting idea, but I don't see a use.
>     The information is already available in /proc/n/status.
>     Is there a compelling argument to duplicate it?
>     Being able to ls -lt /proc doesn't count.

This has been discussed at length in #plan9, and various people
considered it useful, the information is available through
/proc/*/status but in a very inconvenient manner. Currently the mtime
is the box boot time, which is at best useless and at worst confusing.

Knowing when a process was started is extremely convenient,
particularly for long-running or broken procs to know which version of
a program source they corresponds to. If I make a change to abaco
that depends on some new feature of webfs, I'd like to know if I need
to restart webfs or not depending on what version is running, or if I
find a broken proc and I have been hacking on that program during the
last few days, to know roughly what source tree that proc corresponds to.

Also from a security perspective it is very useful to know when a
program was (re)started in case something fishy is going on.

uriel



       reply	other threads:[~2006-03-29 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dfb566242e58a31d6d4f97b379b4f487@plan9.bell-labs.com>
2006-03-29 23:07 ` uriel [this message]
2006-03-29 23:34   ` Russ Cox
2006-03-30  0:13   ` quanstro
2006-03-29 23:34     ` Federico G. Benavento
2006-03-30  8:31   ` Charles Forsyth
2006-03-30 10:09     ` lucio
2006-03-30 11:33     ` Gabriel Diaz
2006-03-30 13:42       ` Anthony Sorace
2006-03-30 14:17         ` Russ Cox
2006-03-30 14:52           ` Gorka guardiola
2006-03-30 16:22             ` uriel
2006-03-30 16:50               ` matt
2006-03-30 17:19                 ` Russ Cox
2006-03-31 10:52                   ` matt
2006-03-30 17:24         ` rog
2006-03-30 17:32           ` uriel
2006-03-30 16:37 Fco. J. Ballesteros

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=790bcfc18f41984ae2b80dd2d05f94c3@cat-v.org \
    --to=uriel@cat-v.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).