You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/05/01 00:23:20 UTC

DO NOT REPLY [Bug 8645] - Microsoft "Services for UNIX v2.0" nfs server has a corrupt last modification date

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8645>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8645

Microsoft "Services for UNIX v2.0" nfs server has a corrupt last modification date





------- Additional Comments From bojan@binarix.com  2002-04-30 22:23 -------
I guess we are off scope, but I don't think it matters - we're trying to resolve
you problem, right?

First, the real reason why I don't like the patch. A quick search through Tomcat
sources reveals that the method lastModified() gets called in a number of
different places, from different code and always relies on the fact that the
timestamp of the file has changed (correctly). So, you would potentially be
fixing a lot more instances. And then there is of course Ant, Velocity and other
Jakarta software that would have to do the same to satisfy a buggy piece of
software. Sometimes that's the only option (for instance a buggy ZIP
implementation in JDK, screwing class reloads from .jar files) since it is core
part of the system and cannot be avoided. But this scenario isn't one of those
things (although I appreciate that it is important to you).

In solution to your problem, why not have the home directories on a Linux box -
then you can have a decent SMB and NFS on the same machine. I have searched the
web for smbfs + autofs and even found a HOWTO. I agree when you say that it is
an unproven concept, but so is Microsoft NFS.

Bojan

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>