Hide Forgot
glusterd should also take care of to set up logging for gsyncd (according to its namespace logic)
*** Bug 2561 has been marked as a duplicate of this bug. ***
Fix in bz #2561 (duplicate) fixes this too.
checked with 3.2.0qa12, gsyncd comes with default log file- ---- gluster volume gsync config :beta1 root.compute.amazonaws.com::slave state_file: /etc/glusterd/gsync/gluster%3A%2F%2F127.0.0.1%3Abeta1/ssh%3A%2F%2Froot%4079.125.76.86%3Agluster%3A%2F%2F127.0.0.1%3Aslave.status log_level: debug ssh_command: ssh -oPasswordAuthentication=no pid_file: /etc/glusterd/gsync/gluster%3A%2F%2F127.0.0.1%3Abeta1/ssh%3A%2F%2Froot%4079.125.76.86%3Agluster%3A%2F%2F127.0.0.1%3Aslave.pid log_file: /usr/local/var/log/glusterfs/gsync/gluster%3A%2F%2F127.0.0.1%3Abeta1/ssh%3A%2F%2Froot%4079.125.76.86%3Agluster%3A%2F%2F127.0.0.1%3Aslave.log remote_gsyncd: /usr/local/libexec/glusterfs/gsyncd gluster_command: /usr/local/sbin/glusterfs -----------------------
its a enhancement..moved to RTNR