You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Rasmus Lerdorf <ra...@apache.org> on 1999/11/12 21:20:37 UTC

Re: OFF TOPIC: Any general apache administration mail lists?

On Fri, 12 Nov 1999, Jeremy Hansen wrote:
> I'm just looking any general apache administration mail lists.  I'm having
> VERY MANY issues with Apache and nfs, specifically file locking and log
> writing via nfs and I'm pretty desperate to figure out what's going on and
> what I can do to fix it.

Problems that are not solved by putting the lock file on the local disk
with:

LockFile /some/local/dir/httpd.lock

?

-Rasmus


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Ask Bjoern Hansen <as...@valueclick.com>.
On Sun, 14 Nov 1999, Manoj Kasichainula wrote:

[...]
> If this is important to you, use a piped logger which sends all
> entries to a central machine for writing.

at ValueClick we use a system like that (s/piped logger/custom apache
module/) for all our logging. Works very well and it was easy to do all
sorts of buffering and stuff for reliability. And in the normal case there
is no disk IO from logging on the webserver (and no multi gigabyte files
to rotate and stuff).


 - ask

-- 
ask bjoern hansen - <http://www.netcetera.dk/~ask/>
more than 60M impressions per day, <http://valueclick.com>


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Manoj Kasichainula <ma...@io.com>.
On Sun, Nov 14, 1999 at 10:16:00AM -0500, Jeremy Hansen wrote:
> I understand what you're saying.  Could you explain reason why the logs
> writes are *not* locked?  

Because they don't have to be. Writes of a certain length are
guaranteed to be atomic. I can't speak for the enjoyable experience
that is NFS, though.

It's not worth the slowdown to lock logs before writing a log entry.
And I believe Apache would have to close and reopen the log file for
every sinle entry for this to work, which is completely insane.

As many people have said already, use separate logs on each server and
combine them before doing log analysis.

> Now I need to write ugly scripts to combine log files

cat log1 log2 log3 > newlog

Log files are also not guaranteed to be ordered, so if your log
analyzer requires that, you'd have to write a script to sort the
entries anyway.

> and it pretty much throws a lot of the
> functionality of WebTrends' auto scheduling and updating out the window
> unless I have my logs sync every 15 minutes.

If this is important to you, use a piped logger which sends all
entries to a central machine for writing.

-- 
Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manojk/


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Jeremy Hansen <je...@xxedgexx.com>.
Thanks for the responses.  I understand better now.  Never really
considered the performance cost of locking log writes from Apache's
perspective.

I think I've come up with a solution though that would allow me to let
things be on separate machines and not have a cheesy script to move things
around.

Let's say I have each web server write to /var/log/httpd which is not
shared via nfs, then on the main server were web trends is running I could
have it nfs mount each web server:

webtrend:/var/log/httpd/{web1,web2,web3}

This would allow me to just use multiple log files in webtrends for one
profile, which you can do simple by separating the files by pipes in the
profile.

Hmm, that would work well, allow all writes to be local and not have the
need of writing scripts to gather and combine and this way I can still use
webtrends' scheduling without fear of things being out of sync.  Cool.

Well, thanks for the help.  Sorry it took me so long to "get it", but I
perceived things to be much easier then what they really are.

-jeremy

> At 10:16am Nov 14, 1999, Jeremy Hansen wrote:
> 
> > I understand what you're saying.  Could you explain reason why the
> > logs writes are *not* locked?
> 
> Performance. If Apache has to be so careful about different pools stepping
> on each others' toes, that's wasted effort. Reliability. What about pool
> failures, stuck NFS connections, etc.? Would there be a possibility that a
> misbehaving pool could lock the log file and in doing so cripple the pools
> running on other servers? Would using a common logfile reintroduce the
> sort of single point of failure that multiple-server setups are supposed
> to prevent? 
> 
> > Now I need to write ugly scripts to combine log files and it pretty
> > much throws a lot of the functionality of WebTrends' auto scheduling
> > and updating out the window unless I have my logs sync every 15
> > minutes.  It just looks ugly to me, that's all.
> 
> Talk to the folks at WebTrends. It is very, very typical for busy Web
> sites to have multiple servers, each recording their own set of log files.
> If WebTrends can't handle that, then thay should see an "opportunity"
> here. ;-)
> 
> -Peter
> 


http://www.xxedgexx.com | jeremy@xxedgexx.com
---------------------------------------------
Y2K.  We're all gonna die.


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Peter W <pe...@usa.net>.
At 10:16am Nov 14, 1999, Jeremy Hansen wrote:

> I understand what you're saying.  Could you explain reason why the
> logs writes are *not* locked?

Performance. If Apache has to be so careful about different pools stepping
on each others' toes, that's wasted effort. Reliability. What about pool
failures, stuck NFS connections, etc.? Would there be a possibility that a
misbehaving pool could lock the log file and in doing so cripple the pools
running on other servers? Would using a common logfile reintroduce the
sort of single point of failure that multiple-server setups are supposed
to prevent? 

> Now I need to write ugly scripts to combine log files and it pretty
> much throws a lot of the functionality of WebTrends' auto scheduling
> and updating out the window unless I have my logs sync every 15
> minutes.  It just looks ugly to me, that's all.

Talk to the folks at WebTrends. It is very, very typical for busy Web
sites to have multiple servers, each recording their own set of log files.
If WebTrends can't handle that, then thay should see an "opportunity"
here. ;-)

-Peter


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Dean Gaudet <dg...@arctic.org>.
On Sun, 14 Nov 1999, Jeremy Hansen wrote:

> [why isn't NFS like a unix filesystem?]

people have been asking that forever.  it just isn't.  expecting NFS to
behave like local disk will get you into lots of troubles.  say no.

Dean


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Jeremy Hansen <je...@xxedgexx.com>.
I understand what you're saying.  Could you explain reason why the logs
writes are *not* locked?  

Also a few people seem to have done what I'm trying to do although it
sound like it may be other platforms besides Linux.  When I attempt to put
the lock file on an nfs volume, any ideas why httpd goes into D state and
the serve hangs?

I'm going to just write to local disks now, but this just seems like
something that should be possible.  I don't know if it's apache's fault or
Linux NFS fault, I'm not a developer but all I keep hearing is "you don't
get it, it's not supposed to do that" which is fine, but it seems like
functionality that could be taken advantage of.  Now I need to write ugly
scripts to combine log files and it pretty much throws a lot of the
functionality of WebTrends' auto scheduling and updating out the window
unless I have my logs sync every 15 minutes.  It just looks ugly to me,
that's all.

Thanks
-jeremy

> Jeremy Hansen wrote:
> > 
> > Again, if this is what I need to do, then I guess I will, but I'dd like to
> > hear more feedback.  Also I'm confused as to what you say about LockFile.
> > This is what the docs read:
> > 
> > The main reason for changing it is if the logs directory is NFS mounted,
> > since the lockfile must be stored on a local disk. The PID of the main
> > server process is automatically appended to the filename.
> 
> I think you are completely missing the point here ... the lock file is
> used (when it is used at all) to serialise the accept() function, which
> some OSes don't like having multiple processes use at the same time on
> the same socket. It has _absolutely nothing to do with logs_, except
> that by default it goes in the same directory.
> 
> Logfiles are simply not locked. They're written with a single write(),
> which is assumed to be atomic. I have no doubt that under NFS it ain't.
> 
> > This sound like what I'm doing, is it not?  Also like I said, using
> > USE_FCNTL_SERIALIZED_ACCEPT I see no httpd.lock file created, I only see
> > it with USE_FLOCK_SERIALIZED_ACCEPT.
> 
> ISTR httpd.lock is unlinked with fcntl(), but can't be with flock(). But
> I could be wrong.
> 
> Cheers,
> 
> Ben.
> 
> --
> http://www.apache-ssl.org/ben.html
> 
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
>      - Indira Gandhi
> 


http://www.xxedgexx.com | jeremy@xxedgexx.com
---------------------------------------------
Y2K.  We're all gonna die.


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Ben Laurie <be...@algroup.co.uk>.
Jeremy Hansen wrote:
> 
> Again, if this is what I need to do, then I guess I will, but I'dd like to
> hear more feedback.  Also I'm confused as to what you say about LockFile.
> This is what the docs read:
> 
> The main reason for changing it is if the logs directory is NFS mounted,
> since the lockfile must be stored on a local disk. The PID of the main
> server process is automatically appended to the filename.

I think you are completely missing the point here ... the lock file is
used (when it is used at all) to serialise the accept() function, which
some OSes don't like having multiple processes use at the same time on
the same socket. It has _absolutely nothing to do with logs_, except
that by default it goes in the same directory.

Logfiles are simply not locked. They're written with a single write(),
which is assumed to be atomic. I have no doubt that under NFS it ain't.

> This sound like what I'm doing, is it not?  Also like I said, using
> USE_FCNTL_SERIALIZED_ACCEPT I see no httpd.lock file created, I only see
> it with USE_FLOCK_SERIALIZED_ACCEPT.

ISTR httpd.lock is unlinked with fcntl(), but can't be with flock(). But
I could be wrong.

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Greg Stein <gs...@lyra.org>.
Normally, Apache places the lock file into the logs directory. If the logs
directory is on an NFS mount (note that Apache can't put its lock file on
an NFS mount), then you must use LockFile to put the lock file on a local
disk.

The lock file is used for handling the accept() call on a web request. It
is unrelated to log files.
[ the fact that the lock file is normally placed into the log directory is
  probably part of the confusion... ]

Now... how to get Apache to lock stuff properly on an NFS mount? Beats me.
I'm a neophyte in that whole area :-)

Cheers,
-g

On Fri, 12 Nov 1999, Jeremy Hansen wrote:
> Again, if this is what I need to do, then I guess I will, but I'dd like to
> hear more feedback.  Also I'm confused as to what you say about LockFile.
> This is what the docs read:
> 
> The main reason for changing it is if the logs directory is NFS mounted,
> since the lockfile must be stored on a local disk. The PID of the main
> server process is automatically appended to the filename.
> 
> This sound like what I'm doing, is it not?  Also like I said, using
> USE_FCNTL_SERIALIZED_ACCEPT I see no httpd.lock file created, I only see
> it with USE_FLOCK_SERIALIZED_ACCEPT.
> 
> Thanks
> -jeremy
> 
> > On Fri, 12 Nov 1999, Jeremy Hansen wrote:
> > > My LockFile currently points to a lock disk, /var/run, the default,
> > > although I never actually see a lock file being created.  I switched to
> > > USE_FLOCK_blah_blah and then I did see the lock file being created, but
> > > Trond explained to me the flock is a BSD style lock and will not work with
> > > Linux NFS locking, only for local locks, and well it didn't work so...
> > 
> > Well, the LockFile directive has nothing to do with locking on log file
> > writes.  The LockFile specifies where the accept queue lock file should
> > go.  This has to do with how incoming requests are handled.
> > 
> > I don't know anything about nfs-based logs.  I have never put myself in a
> > situation where I need to write to the same log file over nfs from many
> > different machines in rapid succession.  The obvious thing I'd say is,
> > "Don't do that!"  Most log file analyzers can merge log files at analysis
> > time.  Given that, why not just make each server log to its own separate
> > file and avoid the locking issue?  
> > 
> > -Rasmus
> > 
> 
> 
> http://www.xxedgexx.com | jeremy@xxedgexx.com
> ---------------------------------------------
> Y2K.  We're all gonna die.
> 

--
Greg Stein, http://www.lyra.org/



Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Jeremy Hansen <je...@xxedgexx.com>.
Again, if this is what I need to do, then I guess I will, but I'dd like to
hear more feedback.  Also I'm confused as to what you say about LockFile.
This is what the docs read:

The main reason for changing it is if the logs directory is NFS mounted,
since the lockfile must be stored on a local disk. The PID of the main
server process is automatically appended to the filename.

This sound like what I'm doing, is it not?  Also like I said, using
USE_FCNTL_SERIALIZED_ACCEPT I see no httpd.lock file created, I only see
it with USE_FLOCK_SERIALIZED_ACCEPT.

Thanks
-jeremy

> On Fri, 12 Nov 1999, Jeremy Hansen wrote:
> > My LockFile currently points to a lock disk, /var/run, the default,
> > although I never actually see a lock file being created.  I switched to
> > USE_FLOCK_blah_blah and then I did see the lock file being created, but
> > Trond explained to me the flock is a BSD style lock and will not work with
> > Linux NFS locking, only for local locks, and well it didn't work so...
> 
> Well, the LockFile directive has nothing to do with locking on log file
> writes.  The LockFile specifies where the accept queue lock file should
> go.  This has to do with how incoming requests are handled.
> 
> I don't know anything about nfs-based logs.  I have never put myself in a
> situation where I need to write to the same log file over nfs from many
> different machines in rapid succession.  The obvious thing I'd say is,
> "Don't do that!"  Most log file analyzers can merge log files at analysis
> time.  Given that, why not just make each server log to its own separate
> file and avoid the locking issue?  
> 
> -Rasmus
> 


http://www.xxedgexx.com | jeremy@xxedgexx.com
---------------------------------------------
Y2K.  We're all gonna die.


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Rasmus Lerdorf <ra...@apache.org>.
On Fri, 12 Nov 1999, Jeremy Hansen wrote:
> My LockFile currently points to a lock disk, /var/run, the default,
> although I never actually see a lock file being created.  I switched to
> USE_FLOCK_blah_blah and then I did see the lock file being created, but
> Trond explained to me the flock is a BSD style lock and will not work with
> Linux NFS locking, only for local locks, and well it didn't work so...

Well, the LockFile directive has nothing to do with locking on log file
writes.  The LockFile specifies where the accept queue lock file should
go.  This has to do with how incoming requests are handled.

I don't know anything about nfs-based logs.  I have never put myself in a
situation where I need to write to the same log file over nfs from many
different machines in rapid succession.  The obvious thing I'd say is,
"Don't do that!"  Most log file analyzers can merge log files at analysis
time.  Given that, why not just make each server log to its own separate
file and avoid the locking issue?  

-Rasmus


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Jim Winstead <ji...@trainedmonkey.com>.
Apache processes running on different servers shouldn't be using
the same accept lock file, so you gain nothing by putting it on an
NFS filesystem. That lockfile has nothing whatsoever to do with
any other file access the servers may do.

But this info from the open(2) man page might be enlightening:

       O_APPEND
               The  file is opened in append mode. Initially, and
               before each write, the file pointer is  positioned
               at  the  end  of  the  file,  as  if  with  lseek.
               O_APPEND may lead to corrupted files on  NFS  file
               systems if more than one process appends data to a
               file at once.  This is because NFS does  not  sup-
               port appending to a file, so the client kernel has
               to simulate it, which can't be done without a race
               condition.

Log to different files. Locking a log file just so you can write
to it would be a complete waste of time.

Jim

On Nov 12, Jeremy Hansen wrote:
> 
> I know I can do this but my feeling is that I shouldn't have to and it
> adds a level of complexity to something that should work, shouldn't it?
> 
> knfsd is supposed to support locking and it appears that it does, but from
> what I understand, Apache has to take advantage of the functions to do so.
> 
> I don't know if I mentioned this, but Trond suggested that I ignore what
> Apache says and put the LockFile ON the nfs volume because having it on
> local disk was a 2.0.x kernel thing and doesn't apply in 2.2.x and knfs's
> case.
> 
> I did that and all my httpd processes went into D state and the web
> servers all hung.
> 
> If I have to, I guess writing to separate logs will be necessary, but it's
> my feeling that if I'm forced to do that, then there's a bug somewhere.
> 
> -jeremy
> 
> > 
> > I can understand using nfs to share Web content on identical servers, esp.
> > if you have a really fast nfs toaster, but why don't you write separate
> > logs and recombine them before running WebTrends. IIRC, it tolerates
> > out-of-sequence log entries. If not, you could use a CustomLog format that
> > adds a timestamp at the beginning of the line, and then do a
> > merge->sort->trim routine at the end.
> > 
> > -Peter
> > 
> > At 3:43pm Nov 12, 1999, Jeremy Hansen wrote:
> > 
> > > I have three web servers being load balanced.  All the servers are
> > > writting their access logs over nfs to the same file.  I'm using Linux
> > > knfsd with kernel's 2.2.12 from Red Hat 6.1 and kernel's 2.2.11-ac3 on the
> > > web servers with nfsv3 client patches from Trond applied.
> > > 
> > > Basically I'm getting very corrupt log files.  Half lines, lines running
> > > into each other, basically everything is telling me that locking is NOT
> > > working.
> > 
> > > So...I don't know what else to explain.  Like I said, if there's a better
> > > list, please let me know, but I'm going crazy trying to get this going.  I
> > > have a perl script I wrote to weed out bad entries so we can run our
> > > reports, btw WebTrends sucks for its tolerance on log file errors, but I
> > > don't know if I'm loosing information or what.
> > 
> > 
> 
> 
> http://www.xxedgexx.com | jeremy@xxedgexx.com
> ---------------------------------------------
> Y2K.  We're all gonna die.
> 
> 

Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Jeremy Hansen <je...@xxedgexx.com>.
I know I can do this but my feeling is that I shouldn't have to and it
adds a level of complexity to something that should work, shouldn't it?

knfsd is supposed to support locking and it appears that it does, but from
what I understand, Apache has to take advantage of the functions to do so.

I don't know if I mentioned this, but Trond suggested that I ignore what
Apache says and put the LockFile ON the nfs volume because having it on
local disk was a 2.0.x kernel thing and doesn't apply in 2.2.x and knfs's
case.

I did that and all my httpd processes went into D state and the web
servers all hung.

If I have to, I guess writing to separate logs will be necessary, but it's
my feeling that if I'm forced to do that, then there's a bug somewhere.

-jeremy

> 
> I can understand using nfs to share Web content on identical servers, esp.
> if you have a really fast nfs toaster, but why don't you write separate
> logs and recombine them before running WebTrends. IIRC, it tolerates
> out-of-sequence log entries. If not, you could use a CustomLog format that
> adds a timestamp at the beginning of the line, and then do a
> merge->sort->trim routine at the end.
> 
> -Peter
> 
> At 3:43pm Nov 12, 1999, Jeremy Hansen wrote:
> 
> > I have three web servers being load balanced.  All the servers are
> > writting their access logs over nfs to the same file.  I'm using Linux
> > knfsd with kernel's 2.2.12 from Red Hat 6.1 and kernel's 2.2.11-ac3 on the
> > web servers with nfsv3 client patches from Trond applied.
> > 
> > Basically I'm getting very corrupt log files.  Half lines, lines running
> > into each other, basically everything is telling me that locking is NOT
> > working.
> 
> > So...I don't know what else to explain.  Like I said, if there's a better
> > list, please let me know, but I'm going crazy trying to get this going.  I
> > have a perl script I wrote to weed out bad entries so we can run our
> > reports, btw WebTrends sucks for its tolerance on log file errors, but I
> > don't know if I'm loosing information or what.
> 
> 


http://www.xxedgexx.com | jeremy@xxedgexx.com
---------------------------------------------
Y2K.  We're all gonna die.



Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Peter W <pe...@usa.net>.
I can understand using nfs to share Web content on identical servers, esp.
if you have a really fast nfs toaster, but why don't you write separate
logs and recombine them before running WebTrends. IIRC, it tolerates
out-of-sequence log entries. If not, you could use a CustomLog format that
adds a timestamp at the beginning of the line, and then do a
merge->sort->trim routine at the end.

-Peter

At 3:43pm Nov 12, 1999, Jeremy Hansen wrote:

> I have three web servers being load balanced.  All the servers are
> writting their access logs over nfs to the same file.  I'm using Linux
> knfsd with kernel's 2.2.12 from Red Hat 6.1 and kernel's 2.2.11-ac3 on the
> web servers with nfsv3 client patches from Trond applied.
> 
> Basically I'm getting very corrupt log files.  Half lines, lines running
> into each other, basically everything is telling me that locking is NOT
> working.

> So...I don't know what else to explain.  Like I said, if there's a better
> list, please let me know, but I'm going crazy trying to get this going.  I
> have a perl script I wrote to weed out bad entries so we can run our
> reports, btw WebTrends sucks for its tolerance on log file errors, but I
> don't know if I'm loosing information or what.



Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Jeremy Hansen <je...@xxedgexx.com>.
 Yes!  I don't want to use this list for something other then what's
 intended, but since you ask :-)
 
 I've actually been working with one of the Linux NFS maintainers, Trond
 Myklebust and so far nothing works in my situation.  I thought LockFile
 and FCNTL in Linux was supposed to do the trick, but well, it's not.
 
 I have three web servers being load balanced.  All the servers are
 writting their access logs over nfs to the same file.  I'm using Linux
 knfsd with kernel's 2.2.12 from Red Hat 6.1 and kernel's 2.2.11-ac3 on the
 web servers with nfsv3 client patches from Trond applied.
 
 Basically I'm getting very corrupt log files.  Half lines, lines running
 into each other, basically everything is telling me that locking is NOT
 working.
 
 Locking does seem to work fine from test programs Trond gave me, but
 Apache is not showing the same information.
 
 My LockFile currently points to a lock disk, /var/run, the default,
 although I never actually see a lock file being created.  I switched to
 USE_FLOCK_blah_blah and then I did see the lock file being created, but
 Trond explained to me the flock is a BSD style lock and will not work with
 Linux NFS locking, only for local locks, and well it didn't work so...
 
 So...I don't know what else to explain.  Like I said, if there's a better
 list, please let me know, but I'm going crazy trying to get this going.  I
 have a perl script I wrote to weed out bad entries so we can run our
 reports, btw WebTrends sucks for its tolerance on log file errors, but I
 don't know if I'm loosing information or what.
 
 Thanks
 -jeremy
 
> > On Fri, 12 Nov 1999, Jeremy Hansen wrote:
> > > I'm just looking any general apache administration mail lists.  I'm having
> > > VERY MANY issues with Apache and nfs, specifically file locking and log
> > > writing via nfs and I'm pretty desperate to figure out what's going on and
> > > what I can do to fix it.
> > 
> > Problems that are not solved by putting the lock file on the local disk
> > with:
> > 
> > LockFile /some/local/dir/httpd.lock
> > 
> > ?
> > 
> > -Rasmus
> > 
> 
> 
> http://www.xxedgexx.com | jeremy@xxedgexx.com
> ---------------------------------------------
> Y2K.  We're all gonna die.
> 
> 
> 
> 


http://www.xxedgexx.com | jeremy@xxedgexx.com
---------------------------------------------
Y2K.  We're all gonna die.


Re: OFF TOPIC: Any general apache administration mail lists?

Posted by Jeremy Hansen <je...@xxedgexx.com>.
Yes!  I don't want to use this list for something other then what's
intended, but since you ask :-)

I've actually been working with one of the Linux NFS maintainers, Trond
Myklebust and so far nothing works in my situation.  I thought LockFile
and FCNTL in Linux was supposed to do the trick, but well, it's not.

I have three web servers being load balanced.  All the servers are
writting their access logs over nfs to the same file.  I'm using Linux
knfsd with kernel's 2.2.12 from Red Hat 6.1 and kernel's 2.2.11-ac3 on the
web servers with nfsv3 client patches from Trond applied.

Basically I'm getting very corrupt log files.  Half lines, lines running
into each other, basically everything is telling me that locking is NOT
working.

Locking does seem to work fine from test programs Trond gave me, but
Apache is not showing the same information.

My LockFile currently points to a lock disk, /var/run, the default,
although I never actually see a lock file being created.  I switched to
USE_FLOCK_blah_blah and then I did see the lock file being created, but
Trond explained to me the flock is a BSD style lock and will not work with
Linux NFS locking, only for local locks, and well it didn't work so...

So...I don't know what else to explain.  Like I said, if there's a better
list, please let me know, but I'm going crazy trying to get this going.  I
have a perl script I wrote to weed out bad entries so we can run our
reports, btw WebTrends sucks for its tolerance on log file errors, but I
don't know if I'm loosing information or what.

Thanks
-jeremy

> On Fri, 12 Nov 1999, Jeremy Hansen wrote:
> > I'm just looking any general apache administration mail lists.  I'm having
> > VERY MANY issues with Apache and nfs, specifically file locking and log
> > writing via nfs and I'm pretty desperate to figure out what's going on and
> > what I can do to fix it.
> 
> Problems that are not solved by putting the lock file on the local disk
> with:
> 
> LockFile /some/local/dir/httpd.lock
> 
> ?
> 
> -Rasmus
> 


http://www.xxedgexx.com | jeremy@xxedgexx.com
---------------------------------------------
Y2K.  We're all gonna die.