The current logsys does not use a file backed mapping for its circular
buffer. It requires a circular buffer managed by the memory manager.
This patch fixes that problem.
This patch also fixes the error handling of the writing of the logsys
fplay buffer to be more correct.
Regards
-steve
In
Hi,
I think corosync starts too early during system initialization.
Current priorities in init.d script seems to be wrong:
corosync-1.2.2-1.1.el5:
# chkconfig: - 20 20
I observe very strange behavior, if it starts as configured I get this error
# corosync-cfgtool -s
Printing ring status.
Local
Hi,
On 6/7/2010 6:27 AM, Vadym Chepkov wrote:
> Hi,
>
> I think corosync starts too early during system initialization.
> Current priorities in init.d script seems to be wrong:
>
> corosync-1.2.2-1.1.el5:
> # chkconfig: - 20 20
>
> I observe very strange behavior, if it starts as configured I g
On Jun 7, 2010, at 12:34 AM, Fabio M. Di Nitto wrote:
>
> There is also a major catch-22 in changing them.
>
> In certain environment it is necessary to start corosync right after the
> network because everything else in the boot process could require for
> example a cluster filesystem available
On 6/7/2010 6:47 AM, Vadym Chepkov wrote:
>
> On Jun 7, 2010, at 12:34 AM, Fabio M. Di Nitto wrote:
>>
>> There is also a major catch-22 in changing them.
>>
>> In certain environment it is necessary to start corosync right after the
>> network because everything else in the boot process could req
