Bug 83770 - anacron should not be run on resume if not an enabled service
anacron should not be run on resume if not an enabled service
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: apmd (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Zdenek Prikryl
Jay Turner
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-07 21:12 EST by Stan Tazuma
Modified: 2015-01-07 19:03 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-07 09:31:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Stan Tazuma 2003-02-07 21:12:26 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120
Netscape/7.01

Description of problem:
/etc/sysconfig/apm-scripts/apmscript
will start anacron if a machine is resumed
from a suspended state, even though the
anacron service is disabled.

On my laptop I normally disable all
cron-related services.  If the anacron
service is disabled, it should never be
started unless I choose to run it manually.

The apmscript should check to see if the
anacron service is enabled before running
anacron.

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


How reproducible:
Always

Steps to Reproduce:
1.  use ntsysv (or equiv.) to disable anacron service
2.  put the machine in suspend mode (apm --suspend)
3.  resume the machine
4.  you will find that anacron is running (and possibly
    updatedb is running, making your disk very busy)
    

Actual Results:  It behaves as described.

Expected Results:  anacron should never run if the anacron
service is disabled.

Additional info:

I first noticed the bug in RedHat 7.1.
It still exists on RedHat 8.0.

As a simple work-around, you can do this:

     mv /etc/anacrontab /etc/anacrontab.save

anacron starts and exits if the anacrontab
does not exist.
Comment 1 Bill Nottingham 2005-03-16 17:01:53 EST
It's intentional to catch anything that should have been run during the suspend
period.
Comment 2 Stan Tazuma 2005-03-17 16:40:06 EST
I don't agree.
If the anacron service was not enabled to run at all,
then nothing should have been run during the suspend period.

So nothing should be run after the resume.
Comment 3 Bill Nottingham 2005-03-17 16:46:55 EST
Perhaps if anacron *and* cron were both off, maybe.
Comment 4 Red Hat Bugzilla 2007-02-05 13:59:57 EST
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
Comment 5 Zdenek Prikryl 2007-08-23 10:39:59 EDT
As wrote Bill Nottingham, It's intentional to catch anything that was missed
during the suspend period, more precisely what cron or/and anacron missed. So, I
think, if cron is running and anacron is not, then, after suspend and resume,
the anacron slould be executed. 

Maybe, if both are not running, then, after suspend and resume, the anacron
should not be executed.

Zdenek

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