Bug 111860 - Check for correct syntax before restart
Check for correct syntax before restart
Product: Fedora
Classification: Fedora
Component: dhcp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
: FutureFeature
: 111861 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2003-12-10 18:41 EST by Diego Torres Milano
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-30 18:32:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch solving the problem (615 bytes, patch)
2003-12-11 17:18 EST, Diego Torres Milano
no flags Details | Diff

  None (edit)
Description Diego Torres Milano 2003-12-10 18:41:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1)

Description of problem:
dhcp should not be stopped when 'service dhcpd restart' was issued and
there's a syntax error in configuration file.
A systax check should be issued before stopping the server.
This prevents problems when the service is critical.

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

How reproducible:

Steps to Reproduce:
1.Edit dhcpd configuration file and introduce some syntax error
2.servive dhcpd restart

Additional info:
Comment 1 Diego Torres Milano 2003-12-11 17:18:43 EST
Created attachment 96484 [details]
Patch solving the problem
Comment 2 Daniel Walsh 2003-12-29 06:45:24 EST
*** Bug 111861 has been marked as a duplicate of this bug. ***
Comment 3 Daniel Walsh 2004-03-25 13:55:26 EST
patch applied in dhcp-3.0.1rc12-4.src.rpm
Comment 4 John Flanagan 2004-12-21 14:42:07 EST
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.