Hi,
I've found this script in the glusterfs source, which appears to be better than
the patch given above:
https://raw.github.com/gluster/glusterfs/master/extras/glusterfs-logrotate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glusterfs (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078657
Title:
I am still seeing this issue on version 3.3.1-1 of the glusterfs-server
packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078657
Title:
glusterd does not reopen log files after logrotate
To
Also, please note that the patch above from Calin Don *does not* resolve
this issue. This is because other Gluster daemons that are running, with
their own logfiles, also need to be HUPed in order to rotate their logs,
such as glustershd.
Also, I note that the log files in
Likewise on the clients, all the logs created by the FUSE clients are
not going to get HUPed. These don't create anything in /var/run so I'm
not sure what the best method to find their PIDs would be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The attachment logrotate-glusterd.patch of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
