linux list all processes owned by me no permissions

LINUX LIST ALL PROCESSES OWNED BY ME NO PERMISSIONS HOW TO

So you could give the user 'splunk' specific read access to these files. If you use POSIX ACLs, you can define additional privs above/beyond the standard Unix permissions model.

Between the umask enabling group-read, the setgid, and the supplemental group, Splunk should be able to read the files. That way, the files will have group-read. You'll also need to change the umask for files written by the syslog server to something more like 007 instead of 022 or 077. (A setgid on a directory makes the kernel create any new files in that directory with the group-ownership set to the group-ownership of the directory itself). From there, you'll need to chmod g+s /var/log (and any other subdirs of /var/log) in order to force the files to be owned by the supplemental group. You could set your /var/log directory (and subdirs) to be owned by group 'syslog' and make the 'syslog' group a supplemental group for the user 'splunk'. In the traditional Unix permissions model, the kernel uses the user/group/other bits to decide if the process in question has the rights to read the file. Giving sudo rights for the user 'splunk' to start splunk as 'root' doesn't help here. The forwarder is running on a Linux CentOS 5.11 system.

LINUX LIST ALL PROCESSES OWNED BY ME NO PERMISSIONS HOW TO

What's the way to get around this? If I remember correctly from things I've heard (and a few of the other Answers posts allude to this), there's some file on the host that can be modified to add the 'splunk' user and grant read-only access to these root-owned files, but I don't know/understand the specifics of how to do that.

Permissions on the file: -rw- root rootĪs I understand it, one of the perks/features of Splunk is that the non-root user (in this case, 'splunk') should be able to be assigned read permissions to all files, even ones that are owned by root.Ĭhanging the permissions on the file won't work because each night when the log rolls over, the permissions will get reset. (The file in question is an SMTP maillog.) When attempting to add a monitor stanza on this file in the nf for the forwarder, I get the following error: Insufficient permissions to read file='/file/location/filename' (hint: Permission denied). However, some log files get written with the read/write access to only the owner (not to any group, and not to others), and the owner is always 'root'. Our general policy is to not run applications on our servers as the 'root' user.

Linux list all processes owned by me no permissions