On Wed, 5 Jul 2000, Joshua Chamas wrote:
> ++Better SessionManagement, more aware of server farms that
> don't have reliable NFS locking. The key here is to have only
> one process on one server in charge of session garbage collection
> at any one time, and try to create this situation with a snazzy
> CleanupMaster routine. This is done by having a process register
> itself in the internal database with a server key created at
> apache start time. If this key gets stale, another process can
> become the master, and this period will not exceed the period
> SessionTimeout / StateManager.
This sounds interesting, but I don't quite understand what you did. The
sessions are stored in a dbm file, right? Don't you still need locking if
all servers are trying to update the same NFS-mounted dbm file? Or am I
totally off on how session storage is implemented?
- Perrin
