:
- Original Message -
From: Sascha Schumann [EMAIL PROTECTED]
To: Jason T.Greene [EMAIL PROTECTED]
Cc: Tom May [EMAIL PROTECTED]; Chris Chabot [EMAIL PROTECTED];
[EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Friday, August 24, 2001 1:49 AM
Subject: Re: [PHP-DEV] Re: Re: sysvsem extention
parent process right before fork. There is no parent
initializer for a php module author
MINIT() is called from the parent process in forking servers.
The mm storage handler uses this hook to instantiate a shared
memory segment and propagate the handle to all child
processes.
- Original Message -
From: Chris Chabot [EMAIL PROTECTED]
To: Jason Greene [EMAIL PROTECTED]
Cc: Sascha Schumann [EMAIL PROTECTED]; Tom May [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, August 24, 2001 11:30 AM
Subject: Re: [PHP-DEV] Re: Re: sysvsem extention
Last, i don't see why the implementation as exists, requires 3
semaphores.
I just looked over the code, and the reason for this is it specifically designed for a
multi-process web environment. The most common method for semaphore initialization is
in the parent process right before
As far as creating the new module goes, it shouldn't be 'to much effort'. The basic
implimentation of system v semaphores
is actualy quite simple, its the usage of sempahores that can be very confusing :-)
sysv sem's are often refered to as the
most difficult to comprehend of the sysv
