Re: [9fans] Strange date/time on some created files

[Bruce Ellis <bruce.ellis@gmail.com>]

it would work if stat on PATH/. returned the server's idea.
this is only feasible for a REPLACE, i think union directroies
should return the 'M'.

brucee

On 2/12/06, Russ Cox <rsc@swtch.com> wrote:
> > At least in Ken fs, you want the access time of the root (to get the
> > current fs time):
> >
> > ; date; ls -ldu /n/boot /
> > Sat Feb 11 17:45:13 PST 2006
> > d-r-xr-xr-x /      0 bootes bootes 0 Feb 11 17:45 /
> > d-rwxrwxr-x M 251502 adm    sys    0 Feb 11 17:45 /n/boot
>
> ls -ld /n /n/boot and you will see they have the same mount number.
>
> > It's done here, 9p1.c:1300,1301:
> >
> >         if(d->qid.path == QPROOT)       /* stat of root gives time */
> >                 d->atime = time();
> >
> > and here, 9p2.c:1431,1432:
> >
> >                 if(d->qid.path == QPROOT)       /* stat of root gives time */
> >                         d->atime = time();
> >
> > I haven't looked to see if fossil does it.
>
> It does, if only because accessing the root updates atime anyway.
>
> But that's not what I was getting at.  If you dial the file server
> yourself and read/write 9P messages, yes, you can get at the
> stat info for a file server root.  But via the usual system calls,
> the stat info for any mounted file server root is invisible.  You
> always see the mount point, never the mounted root.
>
> Russ
>