Designwise I agree it would be preferable for /etc to be unwriteable by
services.
The one thing I'm unclear about is:
"So if the /etc/rabbitmq belongs root, rabbitmq-plugins can write only
if run as root, but then it issues error message because ownership
trouble with rabbitmq daemon, which expects things to be rabbitmq."
Since rabbitmq can't be logged into (by default), an administrator would
only be running rabbitmq-plugins directly as root or sudo. Does the
rabbitmq daemon call rabbitmq-plugins directly, itself? I haven't
reproduced that aspect of the problem, so can you provide additional
directions on how to reproduce an error by the service itself?
** Changed in: rabbitmq-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842408
Title:
rabbitmq-server writes to /etc/rabbitmq
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1842408/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
