Bug 479192 - audit log written whenever cron wakes up, keeps disks spun up
Summary: audit log written whenever cron wakes up, keeps disks spun up
Alias: None
Product: Fedora
Classification: Fedora
Component: audit
Version: 10
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Steve Grubb
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 454582
TreeView+ depends on / blocked
Reported: 2009-01-07 20:46 UTC by Eric Sandeen
Modified: 2010-03-24 19:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-12-18 07:31:58 UTC
Type: ---

Attachments (Terms of Use)
example messages (2.06 KB, text/plain)
2009-01-07 20:46 UTC, Eric Sandeen
no flags Details

Description Eric Sandeen 2009-01-07 20:46:49 UTC
Created attachment 328410 [details]
example messages

I was checking a new F10 system for disk writes on an otherwise idle system, and it seems that each time cron wakes up, it generates audit messages, which causes a write to /var/log/audit/audit.log, which keeps my disks spun up even when I'm not doing anything.  :)

I don't know if the audit is necessary... if not, it might be nice to avoid this.


Comment 1 Eric Paris 2009-01-07 21:10:57 UTC
For most users these are totally useless, I couldn't care less on my machines.

maybe it could be done with some sort of user,never rule

but only being limited to uid, auid, gid, and pid in those rule types seems overly restrictive and couldn't be used to supress these....

Sure seems reasonable to me to come up with some way to turn these off...

Comment 2 Steve Grubb 2009-01-07 21:33:53 UTC
I think you can set some buffering options for the audit daemon which won't write to the disk all the time. Try setting flush = none in auditd.conf.

Comment 3 Eric Sandeen 2009-01-07 21:59:11 UTC
I'm not sure that'll help; if auditd is writing to the log, pdflush will come along & flush it out soon even if auditd isn't syncing (I guess w/something like laptop mode, this could help, though).

Comment 4 Tomas Mraz 2009-02-05 19:08:00 UTC
But crond doesn't write to audit on each wakeup just on each job execution. So if you have jobs scheduled only once an hour it will write to the audit only hourly. The question is whether the system jobs (scheduled by root in /etc/crontab and /etc/cron.d/... files) really have to be audited or not.

Comment 5 Bug Zapper 2009-11-18 10:41:33 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 6 Bug Zapper 2009-12-18 07:31:58 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.