I have modified the source code and its working fine but only below two files permission is not getting change even after modification.
1. cli.log
2. file which contains the mounting information for "mount -t glusterfs" command
1. cli.log
2. file which contains the mounting information for "mount -t glusterfs" command
On Wed, Sep 20, 2017 at 5:20 PM, Kaleb S. KEITHLEY <kkeithle@xxxxxxxxxx> wrote:
On 09/18/2017 09:22 PM, ABHISHEK PALIWAL wrote:
> Any suggestion would be appreciated...
>
> On Sep 18, 2017 15:05, "ABHISHEK PALIWAL" <abhishpaliwal@xxxxxxxxx
> <mailto:abhishpaliwal@gmail.com >> wrote:
>
> Any quick suggestion.....?
>
> On Mon, Sep 18, 2017 at 1:50 PM, ABHISHEK PALIWAL
> <abhishpaliwal@xxxxxxxxx <mailto:abhishpaliwal@gmail.com >> wrote:
>
> Hi Team,
>
> As you can see permission for the glusterfs logs in
> /var/log/glusterfs is 600.
>
> drwxr-xr-x 3 root root 140 Jan 1 00:00 ..
> *-rw------- 1 root root 0 Jan 3 20:21 cmd_history.log*
> drwxr-xr-x 2 root root 40 Jan 3 20:21 bricks
> drwxr-xr-x 3 root root 100 Jan 3 20:21 .
> *-rw------- 1 root root 2102 Jan 3 20:21
> etc-glusterfs-glusterd.vol.log*
>
> Due to that non-root user is not able to access these logs
> files, could you please let me know how can I change these
> permission. So that non-root user can also access these log files.
>
There is no "quick fix." Gluster creates the log files with 0600 — like
nearly everything else in /var/log.
The admin can chmod the files, but when the logs rotate the new log
files will be 0600 again.
You'd have to patch the source and rebuild to get different permission bits.
You can probably do something with ACLs, but as above, when the logs
rotate the new files won't have the ACLs.
--
Kaleb
--
Regards
Abhishek Paliwal
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
