Bug 1712241 - atop INTERVAL HARDCODED
Summary: atop INTERVAL HARDCODED
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: atop
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-21 06:43 UTC by George
Modified: 2019-05-22 00:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-22 00:21:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description George 2019-05-21 06:43:05 UTC 
Description of problem:

atop doesn't seem to be reading the config at /etc/sysconfig/atop
(at least for interval)

Version-Release number of selected component (if applicable):

atop-2.4.0-1.el7.x86_64
How reproducible:
alway


Steps to Reproduce:
1. install atop 
2. edit /etc/sysconfig/atop, make INTERVAL=60
3. systemctl start atop

Actual results:
INTERVAL is still 600
can be seem in systemctl status atop
and log file updated in 10 min intervals

Expected results:
INTERVAL should be 60

Additional info:
Same as Bug 1520475
Comment 1 George 2019-05-22 00:20:32 UTC 
Found the problem.
The default /etc/sysconfig/atop has "INTERVAL" defined not "LOGINTERVAL"
Change it to  use "LOGINTERVAL" and atop is started with the correct interval.
Can the default config file be changed to use LOGINTERVAL.
Note You need to log in before you can comment on or make changes to this bug.