[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: kernfs_getattr
- From: Richard Lowe <richlowe_(_at_)_richlowe_(_dot_)_net>
- Date: Mon, 10 Dec 2001 03:35:48 -0500
I was looking through filesystem code (out of both boredom and
and noticed line 502, in kernfs_vnops.c:
vap->va_ctime = vap->va_ctime;
Which, obviously does nothing and gets optimized away by the compiler.
My question (more to aid my understanding than anything else) is whether
that leaves the ctime uninitialized, or if the value I'm seeing is
something else I haven't noticed perusing the code.
$ perl -e 'print -C "/kern/version"'
is this basically a hint that the file isn't real (although I'd have
thought a ctime of 0 (ala the mtime, and atime), would hint more
strongly at that).
Anyway, it's 3:20, and I guess, I'm being a fool, but right now i'm just
perl -e 'print -M $_, "\n" for (</kern/*>)'
somtimes shows negative values such as "-1.15740740740741e-05"
Again, assuming this is correct behavior, and due to something I'm not
think about, I'd be interested to here what it is, and why.
The machine in question is a p150, running -current from 12/9.
I'm guessing in both cases, I missed something obvious.
But thought i'd ask.
[ Richard Lowe - richlowe - richlowe_(_at_)_richlowe_(_dot_)_net ]
[ http://www.richlowe.net/ ]
Visit your host, monkey.org