tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8645] - Microsoft "Services for UNIX v2.0" nfs server has a corrupt last modification date
Date Wed, 01 May 2002 07:32:24 GMT
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 puckman@taglab.com  2002-05-01 07:32 -------
If I could switch to Linux as our fileserver easily, I would. However a 
significant investment (for a small company like ours) has already been made 
in our infrastructure in terms of both hardware and more importantly man 
hours. We might still buy a new Linux box as a file server, but we want to 
know the exact implications of the current situation before rushing to a 
decision.

As I said in my original letter, the fix 3) I've implemented is probably not 
what we want to have in any codebase. However I'm now more thinking about 
number 4).

Is it reasonable that a change in the modification time of a generated .class 
file invalidates the whole context? I guess from a paranoid point of view, if 
the class file changes, then something serious have happened, and thus some 
serious action should be taken. But what would the implications be if it only 
resulted in a reload of that particular JSP and not the whole context?

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message