From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <dd96c981829f31f99b6328f76691654d@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: patch/list sorry/proc-mtime
From: "Russ Cox" <rsc@swtch.com>
Date: Wed, 29 Mar 2006 18:34:29 -0500
In-Reply-To: <790bcfc18f41984ae2b80dd2d05f94c3@cat-v.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 25cdd71a-ead1-11e9-9d60-3106f5b1d025

> 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