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

interval cannot be customized anymore #13

Closed
Zugschlus opened this issue Nov 17, 2017 · 2 comments
Closed

interval cannot be customized anymore #13

Zugschlus opened this issue Nov 17, 2017 · 2 comments

Comments

@Zugschlus
Copy link
Contributor

This is me forwarding https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861874

The user suggests making the INTERVAL in atop.daily configurable from a defaults file.

The idiom should be something along:
`
#!/bin/bash

CURDAY=date +%Y%m%d
LOGPATH=/var/log/atop
BINPATH=/usr/bin
PIDFILE=/run/atop.pid
INTERVAL=600 # interval 10 minutes

if [ -e "/etc/atop/defaults" ] ; then
. /etc/atop/defaults
fi

`

So that the local user can create a defaults file and have the settings made there honored without the need to modify the script itself.

Greetings
Marc

@ThomasAH
Copy link

ThomasAH commented Feb 2, 2018

I'd like to have this again, too.
I run an interval of 60 seconds on some servers, and up to Debian jessie using the old /etc/default/atop was easy.

For now I just change /usr/share/atop/atop.daily, but this won't survive an update, so being able to set this in a config file (/etc/atop/atop-daily.conf or whatever name) would be nice.

@Atoptool
Copy link
Owner

Atoptool commented Jun 9, 2018

Issue has been solved by introducing configuration file /etc/default/atop to overrule variables LOGOPTS, LOGINTERVAL and LOGGENERATIONS.

@Atoptool Atoptool closed this as completed Jun 9, 2018
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

3 participants