On 06/03/2013 02:54 PM, Eric Duda wrote:
What's the reason corosync process needs to run as root(uid 0)? Why is
there no setuid() to switch to a non-root user after startup?
Corosync requires some root capabilities to do mlock and binding. We
could setuid to a nonroot user after the mlock, but the binding occurs
during runtime and can change dynamically during program execution.
For a long time the binding code has need to be reworked to not be
dynamic. Feel free to submit a patch to that effect which would allow
for a setuid to a more appropriate user (such as corosync).
Regards
-steve
Thanks,
Eric
_______________________________________________
discuss mailing list
[email protected]
http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://lists.corosync.org/mailman/listinfo/discuss
