> On Mon, 20 Sep 1999, Admin Mailing Lists wrote:
>
> >
> > what about the problem where file info retrieved via smbmount gets cached?
> > Is this all within the same scope, or would that be considered a different
>
> file info = inode data? (file size and so on)
>
data, file size, yes :)
> > problem? I know there's a doc in the samba source that suggests turning
> > oplocks off in the registry on the NT server to remedy this, but I've had
> > no luck with them. The problem is quite frustrating when you need
> > real-time updated info for a particular file.
>
> oplocks turned on should make this worse since it allows clients to the NT
> server to cache changes. This will make it take longer for the changes to
> appear to the other clients. If your client does no caching of read data
> you should see changes "immediately" (maybe they were talking about
> smbclient, assuming that does not cache anything).
>
well, oplocks is turned on in NT by default. turning them off per the
samba doc had no effect to the problem below
the situation is this..
Server : NT 4.0sp5. I'm running 3com RADIUS on here in a directory
marked sharebale. There's a log file security.log in the
directory that's continously written to.
Client : Linux libc5, current kernel version 2.2.10..current smbmount
version 2.0.4.
Procedure: mounting NT shareable directory via smbmount. Checking filesize
of security.log file every 3 minutes via program.
Problem : Filesize does not update in real-time when checked. Not with an
ls, not with stat()
-Cygnus
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
admin@intergrafix.net Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://cygnus.ncohafmuta.com http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/