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

Logrotate::Rule Manage Olddir location #42

Open
corey-hammerton opened this issue Sep 12, 2016 · 7 comments
Open

Logrotate::Rule Manage Olddir location #42

corey-hammerton opened this issue Sep 12, 2016 · 7 comments
Labels
bug Something isn't working

Comments

@corey-hammerton
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 3.8.7
  • Ruby: 1.8.7
  • Distribution: CentOS 6.6
  • Module version: 1.4.0

How to reproduce (e.g Puppet code you use)

logrotate::rule{"httpd": "olddir" => "/var/log/httpd/old" ... }

What are you seeing

/etc/logrotate.d/httpd
olddir /var/log/httpd/old

Directory does not exist on the filesystem.

What behaviour did you expect instead

The olddir directory created and maintained on the node's filesystem

Output log

Any additional information you'd like to impart

@robinbowes
Copy link

If I surface the createolddir option, would that fix your issue?

@corey-hammerton
Copy link
Author

Logrotate has a createolddir option? I can't seem to find it in any man page

@robinbowes
Copy link

robinbowes commented Sep 14, 2016

On Centos 6.8:

       createolddir mode owner group
              If the directory specified by olddir directive does not exist, it is created.  mode  specifies
              the  mode  for  the olddir directory in octal (the same as chmod(2)), owner specifies the user
              name who will own the olddir directory, and group specifies the  group  the  olddir  directory
              will belong to. This option can be disabled using the nocreateolddir option.

@corey-hammerton
Copy link
Author

It will win the long run, however for earlier versions we would still have to create that directory manually.

FYI we will not be able to upgrade to CentOS 6.8 or later.

@robinbowes
Copy link

On what platforms/versions are you using this?

@corey-hammerton
Copy link
Author

CentOS 6.0 - 6.6. Some 5.6.

@robinbowes
Copy link

Damn, we claim to support 5, 6, & 7 ;)

I'll see what I can do...

@wyardley wyardley removed the 1 - bug label Sep 16, 2017
@juniorsysadmin juniorsysadmin added bug Something isn't working needs-feedback Further information is requested and removed needs-feedback Further information is requested labels Dec 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants