Maybe in someone else's humble opinion the modification time
(there is no creation time in Plan 9) of /proc should be the time of
the last call to fork or exits, i.e. the last time the directory actually
changed. There isn't an obvious value here.
Overloading mtime for all these purposes
is misguided, as none of them are actually modification times.
Sure, I don't disagree that there are any number of "good" values one
could pop into the mtime & atime. That's the point of discussing it,
"what do people think should go in the mtime & atime"
On FreeBSD they are both the current system time for /proc
My thoughts, but no action, on the subject is that it is perhaps the
concept of mtime and atime that are wrong. They seem to be terms welded
to a disk based system.
If there are plenty of values that *could* be available, shouldn't we be
open to finding a way to expose them ?
