httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: Followup re Apache 1.2.4 - hardwired accept lock ... message (fwd)
Date Sun, 31 Aug 1997 18:02:31 GMT
Randy Terbush wrote:
> 
> > On Sun, 31 Aug 1997, Randy Terbush wrote:
> > 
> > > 
> > > This came up recently when I asked the following question but
> > > received no response. 
> > > 
> > > When Jim, Marc, Dean and I put our heads together on this lockfile 
> > > issue, I had provided some code that located the default lockfile 
> > > location to the same place as the PidFile. That seems to be the 
> > > best way to deal with this IMO. Was there something wrong with that 
> > > approach?
> > 
> > I do not recall that code.  In any case, the pid file is reasonably likely
> > to be on a NFS mounted drive as well.  
> 
> Hmmm. Seems rather counter-intuitive to put PID info on a shared 
> drive, but perhaps that is me. /tmp is probably safe on most 
> systems, but is there a security hole that this could present?
> 
> 

Aren't the docs pretty specific that the location of the LOCKFILE
should NOT be on a NFS fs? So, if the pidfile is located on one,
the admin can still put the lockfile whereever he/she wants.

I think this is pretty much all we can and should do :/

-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
            "Look at me! I'm wearing a cardboard belt!"

Mime
View raw message