9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: patch/list sorry/proc-mtime
Date: Wed, 29 Mar 2006 18:34:29 -0500	[thread overview]
Message-ID: <dd96c981829f31f99b6328f76691654d@swtch.com> (raw)
In-Reply-To: <790bcfc18f41984ae2b80dd2d05f94c3@cat-v.org>

> This has been discussed at length in #plan9

Given the things that get discussed at length in #plan9,
let's just say I don't give much weight to that argument.

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

Actually it is the time that the kernel (specifically pc.$O or pccpu.$O etc.)
was built.  It's not useless, and it's the same as essentially every other
device file in the system.  If it were different, I would find that confusing.
Just because you're confused doesn't mean everyone is.

> Knowing when a process was started is extremely convenient,

cat >$home/bin/rc/when <<'EOF'
#!/bin/rc
for(i)
	echo $i `{date `{awk -v n'='^`{date -n} '{printf "%u", n-$6/1000}' /proc/$i/status}}
EOF

Russ



  reply	other threads:[~2006-03-29 23:34 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
2006-03-29 23:34   ` Russ Cox [this message]
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=dd96c981829f31f99b6328f76691654d@swtch.com \
    --to=rsc@swtch.com \
    --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).