Apache won't start, semaphores exhausted

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On 10/4/05, Aleksandar Milivojevic <alex@xxxxxxxxxxxxxxx> wrote:
> Fong Vang wrote:
>
> > (or why the system does not release the semaphore if Apache
> > is no longer running).
>
> Because IPC resources (semaphores, message queues and shared memory
> segments) are not tied to a process, an process simply has access to
> them (and can request for resource to be created or destroyed).  It is
> perfectly OK for a process to create any IPC resource, exit, and then
> some other process started at a later time to pick it up.  If something
> is allocating IPC resources and not cleaning up behind itself, than it
> is a bug in application (where application != process).  IPCs are
> outside of that nice box called process, so you should think outside of
> the box too.

Makes sense.  So looks like there's a semaphore leak.  The owner of
the semaphore is the "apache" user.  Is this most likely Apache or
could it be something else?

Is there a way to have the system automatically cleanup?

thanks for the help.

> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux