On Jul 15, 2014 8:46 PM, Tomlinson, Stuart st0...@intl.att.com wrote:
[ please excuse the poor formatting due to email client ]
From: Jeff Trawick [mailto:traw...@gmail.com]
On Tue, Jul 15, 2014 at 4:55 PM, Tomlinson, Stuart st0...@intl.att.com
wrote:
Hello,
We have experienced this
On Wed, Jul 16, 2014 at 12:49 PM, Jeff Trawick traw...@gmail.com wrote:
On Jul 15, 2014 8:46 PM, Tomlinson, Stuart st0...@intl.att.com wrote:
Are there any expected negative impacts from using sysvsem instead of
sem (which I understand defaults to posixsem - described in the
documentation as
On Wed, Jul 16, 2014 at 7:20 AM, Yann Ylavic ylavic@gmail.com wrote:
On Wed, Jul 16, 2014 at 12:49 PM, Jeff Trawick traw...@gmail.com wrote:
On Jul 15, 2014 8:46 PM, Tomlinson, Stuart st0...@intl.att.com
wrote:
Are there any expected negative impacts from using sysvsem instead of
On Wed, Jul 16, 2014 at 1:30 PM, Jeff Trawick traw...@gmail.com wrote:
I won't disagree with you at all Yann, but in the interest of promoting the
idea that you don't actually have to use all the configuration httpd offers:
If the poster had not made a change from the default based on some
Hello,
We have experienced this warning/error a few times:
[Thu Jul 03 20:17:15 2014] [warn] (4)Interrupted system call: Failed to acquire
SSL session cache lock
After this has occurred, the Apache ErrorLog is flooded with these errors:
[Thu Jul 03 20:17:57 2014] [error] shmcb_subcache_retrieve
On Tue, Jul 15, 2014 at 4:55 PM, Tomlinson, Stuart st0...@intl.att.com
wrote:
Hello,
We have experienced this warning/error a few times:
[Thu Jul 03 20:17:15 2014] [warn] (4)Interrupted system call: Failed to
acquire SSL session cache lock
After this has occurred, the Apache ErrorLog is
[ please excuse the poor formatting due to email client ]
From: Jeff Trawick [mailto:traw...@gmail.com]
On Tue, Jul 15, 2014 at 4:55 PM, Tomlinson, Stuart st0...@intl.att.com
wrote:
Hello,
We have experienced this warning/error a few times:
[Thu Jul 03 20:17:15 2014] [warn]
