[Bugs] [Bug 1286959] [GlusterD]: After log rotate of cmd_history.log file, the next executed gluster commands are not present in the cmd_history.log file.

bugzilla at redhat.com bugzilla at redhat.com
Thu Feb 4 21:51:57 UTC 2016


--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/12832 committed in master by Niels de Vos
(ndevos at redhat.com) 
commit 8fdfa0c17cf492f39e675f7502596754f6e5aeb4
Author: Gaurav Kumar Garg <garg.gaurav52 at gmail.com>
Date:   Tue Dec 1 14:23:08 2015 +0530

    libglusterfs: close & open cmd_history.log on log rotate

    Post log rotate, cmd_history.log is not refreshed (closed & opened back)
    due to which new commands still land up in the log rotated file.

    Fix is to close and open cmd_history.log file upon log rotation

    Change-Id: Ie6990c9d55b0afa544bc5c84de3db49ff4b1299b
    BUG: 1286959
    Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Reviewed-on: http://review.gluster.org/12832
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>

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

More information about the Bugs mailing list