[Bugs] [Bug 1213796] systemd integration with glusterfs

[bugzilla at redhat.com]

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

Niels de Vos <ndevos at redhat.com> changed:

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



--- Comment #2 from Niels de Vos <ndevos at redhat.com> ---
I am not sure if socket activation makes a lot of sense here. Gluster clients
may already know what bricks are available. When a Gluster Server reboots,
glusterd should start the brick processes. When socket activation is used,
glusterd will only start after a connection on the socket (unix socket or tcp
port) is detected. I think gluster clients can try to connect to the brick
processes without touching any of the glusterd sockets.

What is the use-case you are trying to solve here?

-- 
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=ywNadJjZ1i&a=cc_unsubscribe