Bug 763886 (GLUSTER-2154) - Move .cmd_log_history to log directory
Summary: Move .cmd_log_history to log directory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2154
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.1.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-25 07:53 UTC by Vijay Bellur
Modified: 2011-05-04 08:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTA
Mount Type: ---
Documentation: DNR
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Anand Avati 2010-11-25 05:34:16 UTC 
PATCH: http://patches.gluster.com/patch/5781 in master (mgmt/glusterd: Move .cmd_log_history to log directory)
Comment 1 Vijay Bellur 2010-11-25 07:53:31 UTC 
.cmd_log_history should move to log directory instead of /etc/glusterd as it exists today.
Comment 2 Raghavendra Bhat 2011-02-18 03:11:06 UTC 
fixed. .cmd_log_history is not there in /etc/glusterd anymore. Its present in the log file directory.



root@bigbang:/home/raghu# ls -a /etc/glusterd/
.  ..  glusterd.info  nfs  peers  vols
root@bigbang:/home/raghu# ls -a /usr/local/var/log/glusterfs/
.  ..  bricks  .cmd_log_history  mnt-client.log  nfs.log  pid_negative-.log  usr-local-etc-glusterfs-glusterd.vol.log
root@bigbang:/home/raghu#
Note You need to log in before you can comment on or make changes to this bug.