Issue

• A particular message is not affected with 'no-msg-id' in brick-log-format option.
  'gluster volume set diagnostics.brick-log-format no-msg-id' seems not to change the behaviour to no-msg-id.
  For example, at the time of 'service glusterd stop/start', I got following logs.

  [2014-12-05 01:57:30.588737] I [MSGID: 100030] [glusterfsd.c:1998:main] 0-/usr/sbin/glusterfsd: Started running /usr/sbin/glusterfsd version 3.6.0.28 (args: /usr/sbin/glusterfsd -s rhs3-node1 --volfile-id testvol.rhs3-node1.brick-bricksr
  v1 -p /var/lib/glusterd/vols/testvol/run/rhs3-node1-brick-bricksrv1.pid -S /var/run/cf16889c59bff5e0fb74b2c347151534.socket --brick-name /brick/bricksrv1 -l /var/log/glusterfs/bricks/brick-bricksrv1.log --xlator-option *-posix.glusterd-u
  uid=b976e2f5-ad28-4556-aea9-7398290fdff2 --brick-port 49152 --xlator-option testvol-server.listen-port=49152)
  

• Why is the messages shown even though the brick-log-format set as no-msg-id?