Red Hat Bugzilla – Bug 476306
autofs not started at boot
Last modified: 2009-12-18 02:16:28 EST
Description of problem: autofs not started at boot when installed
Version-Release number of selected component (if applicable):
How reproducible: Very
Steps to Reproduce:
1. yum install autofs
2. chkconfig --list |grep autofs
3. note autofs not enabled
autofs should be enabled, or prompted that it is not with %post macro of spec
Ian, correct me if I'm wrong, but I think it's that way because autofs used to get installed by default, and folks didn't want yet another thing starting that they didn't use. Is that right? Does autofs no longer get installed by default?
It's marked as optional in the comps so I guess the answer is
But I think that's not the question.
The question here is does a "chkconfig --add autofs" enable
autofs to start in the run levels specified in the "chkconfig:"
line in the init script, which I believe it should. As the
add is done in the %post script at install.
autofs does get started, however, as there is no network available NFS does not work.
This just seemed odd to me and follows the same theme as bug 476382 (ypbind).
If it is now the default for F10 to not start networking at boot (which would seem odd, as it default to init 5), then when you install autofs it would seem to make sense to verify the status of the 'network' service to see if it is 'on'. If not then it could either:
a) inform you of this
b) chkconfig network on
(In reply to comment #3)
> To clarify.
> autofs does get started, however, as there is no network available NFS does not
Your assuming that autofs starts in run level 2 (where
networking is not started) by default which is not the
I am aware of this, but F10 was at init 5 and init 5 is documented in inittab as 'full multiuser with network and X'.
In anycase, I put Fedora to init 3, just in case, and there was still no networking, therefore no NFS.
It just seems a little disjointed.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.