From: "G.W. Haywood" <[EMAIL PROTECTED]> > On Tue, 7 Nov 2000, Daniel Little wrote: > > > Has anyone had any problems with failure to write locks on > Apache:ASP > > under Solaris or any other platform? > > I just grepped one of my logfiles (a small one, about 70 megabytes:) > and there was no occurrence of this message. Linux 2.2.16, Perl > 5.6.0, Apache 1.3.12, mod_perl 1.24, ASP 0.19 (yes, 0.19). I did it > on this log because it's the only server (in development) I've got > which is running 5.6.0. There are only two things different to that on our environment - ASP 2.03 (instead of 0.19 - ouch!) and Solaris 2.7 (instead of Linux 2.2.16). All the rest are the same (and we're on a Sparc - I presume yours is Intel?). > Solaris does funny things sometimes, but I think Josh might have > something to say about this one if you're patient. Sure, I can wait for Josh's response. We had to backout our Solaris version this A.M. due to these problems. Note, we did find the problem with the form variables that were just showing up as plain incorrect. All I can say is 'use strict;' - it pays. I had some difficulties with 'use strict;' on NT about a year ago and when we moved the platform to UNIX, had a number of issues around variables getting clobbered, getting lost entirely, etc., and switching to using strict with all variables assigned in the ASP script solved the problems. I guess that's what I get for practicing unsafe code practices... ;) Anyway, thanks for the response. I think we're going to have to build a load test platform to reproduce the bugs without going live. Most of these problems did not show up in more than three months of testing the environment. Sigh. Daniel.
begin:vcard n:Little;Daniel fn:Daniel Little tel;cell:(204) 955-0300 tel;fax:(204) 487-6680 tel;work:(204) 837 5503 url:http://www.metrex.net org:Metrex Systems Consulting Inc.; version:2.1 email;internet:[EMAIL PROTECTED] title:President end:vcard
