Bug 436461 - crond not condrestarted at upgrade
crond not condrestarted at upgrade
Status: CLOSED DUPLICATE of bug 434657
Product: Fedora
Classification: Fedora
Component: vixie-cron (Show other bugs)
8
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Marcela Mašláňová
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-07 07:26 EST by Jon Ciesla
Modified: 2008-03-07 08:03 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-07 08:03:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jon Ciesla 2008-03-07 07:26:35 EST
Description of problem:


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

How reproducible:
Upgrade from previous version didn't restart crond, which caused failures with
pam errors of several cron jobs.  Restarting crond manually fixed the issue.
Comment 1 Marcela Mašláňová 2008-03-07 08:03:15 EST

*** This bug has been marked as a duplicate of 434657 ***

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