- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Why is the access mode of the usersync.log 600 ?
- Labels:
-
Apache Ranger
Created ‎01-27-2016 10:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I built the hadoop cluster included the Ranger service with the Ambari.
When I checked the usersync.log, I needed the sudo command.
On the other hands, the logs for the ranger-admin allow anyone to read.
Why is the access mode of the usersync.log 600 ?
Created ‎01-27-2016 11:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's because of security. Usesysnc gets the information from AD/LDAP when we sync it with corporate AD.
I have the same.
-rw-------. 1 ranger ranger 563040 Jan 14 23:59 usersync.log.2016-01-14
-rw-------. 1 ranger ranger 563040 Jan 15 23:59 usersync.log.2016-01-15
-rw-------. 1 ranger ranger 561917 Jan 16 23:59 usersync.log.2016-01-16
-rw-------. 1 ranger hadoop 558360 Jan 17 23:59 usersync.log.2016-01-17
-rw-------. 1 ranger hadoop 557551 Jan 18 23:59 usersync.log.2016-01-18
-rw-------. 1 ranger hadoop 558964 Jan 19 23:59 usersync.log.2016-01-19
-rw-------. 1 ranger hadoop 560416 Jan 20 23:59 usersync.log.2016-01-20
-rw-------. 1 ranger hadoop 558842 Jan 21 23:59 usersync.log.2016-01-21
-rw-------. 1 ranger hadoop 558720 Jan 22 23:59 usersync.log.2016-01-22
-rw-------. 1 ranger hadoop 560172 Jan 23 23:59 usersync.log.2016-01-23
-rw-------. 1 ranger hadoop 559214 Jan 24 23:59 usersync.log.2016-01-24
-rw-------. 1 ranger hadoop 559784 Jan 25 23:59 usersync.log.2016-01-25
-rw-------. 1 ranger hadoop 558720 Jan 26 23:59 usersync.log.2016-01-26
[root@phdns01 usersync]#
Created ‎01-27-2016 11:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's because of security. Usesysnc gets the information from AD/LDAP when we sync it with corporate AD.
I have the same.
-rw-------. 1 ranger ranger 563040 Jan 14 23:59 usersync.log.2016-01-14
-rw-------. 1 ranger ranger 563040 Jan 15 23:59 usersync.log.2016-01-15
-rw-------. 1 ranger ranger 561917 Jan 16 23:59 usersync.log.2016-01-16
-rw-------. 1 ranger hadoop 558360 Jan 17 23:59 usersync.log.2016-01-17
-rw-------. 1 ranger hadoop 557551 Jan 18 23:59 usersync.log.2016-01-18
-rw-------. 1 ranger hadoop 558964 Jan 19 23:59 usersync.log.2016-01-19
-rw-------. 1 ranger hadoop 560416 Jan 20 23:59 usersync.log.2016-01-20
-rw-------. 1 ranger hadoop 558842 Jan 21 23:59 usersync.log.2016-01-21
-rw-------. 1 ranger hadoop 558720 Jan 22 23:59 usersync.log.2016-01-22
-rw-------. 1 ranger hadoop 560172 Jan 23 23:59 usersync.log.2016-01-23
-rw-------. 1 ranger hadoop 559214 Jan 24 23:59 usersync.log.2016-01-24
-rw-------. 1 ranger hadoop 559784 Jan 25 23:59 usersync.log.2016-01-25
-rw-------. 1 ranger hadoop 558720 Jan 26 23:59 usersync.log.2016-01-26
[root@phdns01 usersync]#
Created ‎01-27-2016 11:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your prompt reply. I'm happy now.
