On Thu, Jun 04, 2009 at 08:54:26AM +0200, Florian Haas wrote:
> On 06/04/2009 08:42 AM, Andrew Beekhof wrote:
> > On Thu, Jun 4, 2009 at 8:40 AM, Florian Haas wrote:
> >> Andrew, Dejan et al.,
> >>
> >> The TODO page at http://clusterlabs.org/wiki/TODO states that Pacemaker
> >> now automagically
On 06/04/2009 08:42 AM, Andrew Beekhof wrote:
> On Thu, Jun 4, 2009 at 8:40 AM, Florian Haas wrote:
>> Andrew, Dejan et al.,
>>
>> The TODO page at http://clusterlabs.org/wiki/TODO states that Pacemaker
>> now automagically sets the kernel.core_uses_pid sysctl to ease
>> debugging. Wouldn't it mak
On Thu, Jun 4, 2009 at 8:40 AM, Florian Haas wrote:
> Andrew, Dejan et al.,
>
> The TODO page at http://clusterlabs.org/wiki/TODO states that Pacemaker
> now automagically sets the kernel.core_uses_pid sysctl to ease
> debugging. Wouldn't it make sense to check the currently set "ulimit -c"
> too,
Andrew, Dejan et al.,
The TODO page at http://clusterlabs.org/wiki/TODO states that Pacemaker
now automagically sets the kernel.core_uses_pid sysctl to ease
debugging. Wouldn't it make sense to check the currently set "ulimit -c"
too, and at least issue a warning message on startup if that ulimit