Bug 815823 - /sbin/chkconfig autofs returns wrong exit code
/sbin/chkconfig autofs returns wrong exit code
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: autofs (Show other bugs)
16
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ian Kent
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-24 11:28 EDT by John Florian
Modified: 2012-04-24 11:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-24 11:50:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Patch that fixes the problem; declare location of PID file to satisfy systemd. (380 bytes, patch)
2012-04-24 11:28 EDT, John Florian
no flags Details | Diff

  None (edit)
Description John Florian 2012-04-24 11:28:43 EDT
Created attachment 579893 [details]
Patch that fixes the problem; declare location of PID file to satisfy systemd.

Description of problem:
Puppet will perpetually try restart the autofs service because it's detection technique for this service gets the wrong results. The recent update to systemd has broken many of the legacy init scripts and this is one example.

Version-Release number of selected component (if applicable):
autofs-5.0.6-5.fc16.x86_64

How reproducible:
always

Steps to Reproduce:
Should be able to use 'chkconfig autofs; echo $?' but for some reason I cannot validate that way.  It gives the correct result.  However puppet testing confirms the problem does exist and the typical fix works here too --  see patch.
Comment 1 John Florian 2012-04-24 11:50:57 EDT
I completely hosed this bug report with bad info.  Will create another with accurate details.

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