Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemd service permissions #98

Closed
ludusregio opened this issue Jun 28, 2017 · 2 comments
Closed

systemd service permissions #98

ludusregio opened this issue Jun 28, 2017 · 2 comments

Comments

@ludusregio
Copy link

My logs are full of following messages:

Jun 28 14:51:59 servername systemd: Configuration file /etc/systemd/system/splunk.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Jun 28 14:51:59 servername systemd: Configuration file /etc/systemd/system/splunk.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.

This is due to the file /etc/systemd/system/splunk.service having the execute bit set for the owner and not read to world. Can this be corrected in the following code? Instead of mode 700, mode 644?

 template '/etc/systemd/system/splunk.service' do
    source 'splunk-systemd.erb'
    mode '700'
    variables(
      splunkdir: splunk_dir,
      runasroot: node['splunk']['server']['runasroot']
    )
  end
@tas50
Copy link
Contributor

tas50 commented Sep 9, 2017

I’m adding the Type: Jump In GitHub label to this issue. This is a great issue for someone to get their feet wet with and we’d love a PR to resolves the issue.

@k4ved k4ved mentioned this issue Oct 20, 2017
4 tasks
@tas50 tas50 closed this as completed Nov 7, 2017
@tas50
Copy link
Contributor

tas50 commented Nov 7, 2017

Fixed and soon to be released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants