[Bugs] [Bug 1213796] systemd integration with glusterfs

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1213796

Sachidananda Urs <surs at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(surs at redhat.com)  |



--- Comment #3 from Sachidananda Urs <surs at redhat.com> ---
GlusterD would anyway start upon reboot. The usecase here is... admin/user has
the privilege to enable and start glusterd.socket (on need by basis) and not be
bothered about restarting glusterd (In case the process gets killed due to
crash or OOM kill or by any other means)... it does get automatically started
by next vol info or any other volume command. Failure does not go unnoticed, it
is handled by systemd for further diagnosis.

Of course we have to document about not using this feature while using quorum.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=dgF1BhbjSo&a=cc_unsubscribe