Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 166773 - ntp %post scriptlet fails on upgrade, if ntpd is disabled.
ntp %post scriptlet fails on upgrade, if ntpd is disabled.
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: ntp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miroslav Lichvar
Brian Brock
Depends On:
Blocks: 181409
  Show dependency treegraph
Reported: 2005-08-25 11:34 EDT by Charlie Brady
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHSA-2006-0393
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-10 14:25:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
ntp-4.2.0.a.20050816-3.src.rpm (2.40 MB, patch)
2005-10-31 05:44 EST, Petr Raszyk
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0393 normal SHIPPED_LIVE Low: ntp security update 2006-08-10 00:00:00 EDT

  None (edit)
Description Charlie Brady 2005-08-25 11:34:53 EDT
This was reportedly fixed for FC1, but persists in RHEL4. See:


To fix, change:

    # start ntp if it was running previously
    [ $wasrunning -eq 0 ] && service ntpd start > /dev/null 2>&1


    # start ntp if it was running previously
    if [ $wasrunning -eq 0 ]; then service ntpd start > /dev/null 2>&1 ; fi

(or do something else so that exit status of script is 0).
Comment 1 Petr Raszyk 2005-10-31 05:41:41 EST

 # start ntp if it was running previously
 [ $wasrunning -eq 0 ] && service ntpd start > /dev/null 2>&1 || :
Comment 2 Petr Raszyk 2005-10-31 05:44:06 EST
Created attachment 120556 [details]
Comment 8 Red Hat Bugzilla 2006-08-10 14:25:08 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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