Date: Wed, 16 Dec 1998 15:20:49 -0800 From: Mike Smith <mike@smith.net.au> To: Paul van der Zwan <paulz@trantor.stuyts.nl> Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server Message-ID: <199812162320.PAA01606@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 16 Dec 1998 23:33:53 %2B0100." <199812162233.XAA00548@trantor.stuyts.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
> To test my theory that the -1 times are causing the error because they violate > the protocol, I chanded the #define nfsm_v3sattr in /usr/src/sys/nfs/ > nfsm_subs.h to use NFSV3SATTRTIME_TOSERVER in stead of NFSV3SATTRTIME_TOCLIENT. > This makes the server ignore the time values. My test program now creates > poth testfile1 and testfile2. This means that the files get the server's timestamp, which is going to break things like make(1) which expect files to be created with the client's time. > I might be wrong but I think the bug is in the client code and surfaced because > Solaris 7 has become stricter about clients adhering to the protocol specs. This sounds like a good starting point; any chance of tracking down where the time values are supposed to be set in the FreeBSD code and fixing that, since that's what seems to be wrong...? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812162320.PAA01606>