samba - Mar 2002 - apache logs -> samba -> windows file locking question

Samba version 2.2.3a
Redhat Linux 7.2

I have a windows server that connects to my linux web server and copies the logs
locally (to the windows server) to process.   The windows machine connects to
the samba share every 30 minutes to copy the log again.  Almost everything works
fine.  Since apache keeps the access_log open at all times I am pretty sure that
I am going to run into some locking problems.  Actually, I believe that I am
having locking issues.  Every night at 12 a new log is generated.  What would be
the best way to handle this ?

The samba share is mounted as Read-Only

I have been trying:

veto oplock files = ex*.log
and/or
fake oplocks = Yes

Is there anything else I can do ?  Please let me know.  

Thanks,

Matt
-------------- next part --------------
HTML attachment scrubbed and removed

i don't think oplocks is going to work with apache.
the log file is not locked at all by apache or linux. it
is simply an open file that is being written to.  what
makes you think you are running into locking issues?

i assume that when a new log is generated, the old one
is getting renamed to access_log.1 or something similar.
you can access this log without worrying about many
racing conditions, since nothing will write to this file,
except that it will be incremented to the next higher
number once per day.  to understand the details
of this process and modify its behavior:
man logrotate
less /etc/logrotate.d/apache

hth,

cliff

"Matthew J. Salerno" wrote:
> Samba version 2.2.3aRedhat Linux 7.2 I have a windows server that connects
to my linux web server
> and copies the logs locally (to the windows server) to process.   The
windows machine connects to
> the samba share every 30 minutes to copy the log again.  Almost everything
works fine.  Since
> apache keeps the access_log open at all times I am pretty sure that I am
going to run into some
> locking problems.  Actually, I believe that I am having locking issues. 
Every night at 12 a new
> log is generated.  What would be the best way to handle this ? The samba
share is mounted as
> Read-Only I have been trying: veto oplock files = ex*.logand/orfake oplocks
= Yes Is there
> anything else I can do ?  Please let me know. Thanks, Matt
--
___cliff rayman___cliff@genwax.com___http://www.genwax.com/