Bug 468956 - on shutdown, stopping anacron fails
Summary: on shutdown, stopping anacron fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anacron
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-29 05:26 UTC by Andre Robatino
Modified: 2008-10-29 13:42 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-10-29 13:42:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andre Robatino 2008-10-29 05:26:47 UTC
Description of problem:
If one uses Alt-F7 to see the shutdown messages (unfortunately they don't show by default due to bug #439699), there are two "Stopping anacron" messages.  The second one always fails, the first may or may not fail.

Version-Release number of selected component (if applicable):
anacron-2.3-61.fc9.i386

How reproducible:
always

Steps to Reproduce:
1.  Shutdown and use Alt-F7 to see shutdown messages.

Additional info:
I don't remember when this started but it was probably within the last month or two.  Sorry I can't be more specific.  I've seen this in two F9 fully updated clean installs, one running in VirtualBox with a Windows XP host.

Comment 1 Marcela Mašláňová 2008-10-29 09:53:35 UTC
Please try anacron-2.3-62.fc9 and let me know.

Comment 2 Andre Robatino 2008-10-29 10:15:23 UTC
With anacron-2.3-62.fc9, there are no "stopping anacron" messages at all. I checked System/Administration/Services and anacron is enabled but stopped.  Is this all normal default behavior?  I never made any anacron-related changes manually.

Comment 3 Marcela Mašláňová 2008-10-29 13:42:20 UTC
Yes, that's intended behaviour. This daemon lives only as long as its has something to do, then stopped itself. Usually it runs yours cron.daily jobs after switching on your computer (with some delay) once a day.

I was interested in problem with "double stopping". So it looks like this problem was fixed. Please feel free to reopen it, if your problem persist.


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