Brian,
thanks for reporting this bug. I've already sent patch to fix this behavior.
Regards,
Honza
Brian J. Murrell napsal(a):
> I seem to have found a bug in the corosync.conf parser with corosync
> 1.4.1.
>
> If you forget to set the "name" of a service as such:
>
> service {
> ver: 1
> }
>
> corosync will segfault starting up. Admittedly the above configuration
> is invalid but corosync shouldn't segfault on it. Printing some useful
> error message would be ideal.
>
> Cheers,
> b.
>
>
> _______________________________________________
> discuss mailing list
> discuss@xxxxxxxxxxxx
> http://lists.corosync.org/mailman/listinfo/discuss
>
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
