On 07/05/2011 07:20 PM, Tim Beale wrote:
Hi,
We've just upgraded to corosync v1.3.1 and struck a problem with corosync
failing to startup. The problem is the getpwnam_r()/getgrnam_r() calls return
ERANGE on our system, meaning insufficient buffer space was supplied (the
expected buffer
Hi,
We've just upgraded to corosync v1.3.1 and struck a problem with corosync
failing to startup. The problem is the getpwnam_r()/getgrnam_r() calls return
ERANGE on our system, meaning insufficient buffer space was supplied (the
expected buffer length is 256, rather than 250).
I don't know much