Bug 193798

Summary: autofs has incorrect test for a config file in /etc/init.d/autofs
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: jmoyer
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-06-16 00:22:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2006-06-01 18:08:38 UTC
Description of problem:

I was wondering why changes in /etc/sysconfig/autofs, and in particular
seting OPTIONS there, have no effect in a startup.  After looking closer
at /etc/init.d/autofs  I found that this does

if [ -x $confdir/autofs ]; then
        . $confdir/autofs
fi

while $confdir/autofs is NOT, and rightly so, executable.

After replacing '-x' with '-r' things started to work as expected.

Version-Release number of selected component (if applicable):
autofs-5.0.0_beta3-6

Comment 1 Ian Kent 2006-06-02 01:30:09 UTC
(In reply to comment #0)

Thanks again Michal.

> Description of problem:
> 
> I was wondering why changes in /etc/sysconfig/autofs, and in particular
> seting OPTIONS there, have no effect in a startup.  After looking closer
> at /etc/init.d/autofs  I found that this does

As it turns out this is the only option that is effected by this
as the config is read by the daemon itself at startup, except for
the OPTIONS variable which is meant for the init script only.

Oops.

I'll change the test in the init script straight away.

Ian


Comment 2 Ian Kent 2006-06-02 11:02:53 UTC
(In reply to comment #1)
> (In reply to comment #0)
> 
> Thanks again Michal.
> 
> > Description of problem:
> > 
> > I was wondering why changes in /etc/sysconfig/autofs, and in particular
> > seting OPTIONS there, have no effect in a startup.  After looking closer
> > at /etc/init.d/autofs  I found that this does
> 
> As it turns out this is the only option that is effected by this
> as the config is read by the daemon itself at startup, except for
> the OPTIONS variable which is meant for the init script only.
> 
> Oops.
> 
> I'll change the test in the init script straight away.
> 

Done.
Look for a new version of autofs autofs-5.0.0_beta4-1.

Ian



Comment 3 Ian Kent 2006-06-16 00:22:50 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > (In reply to comment #0)
> > 
> > Thanks again Michal.
> > 
> > > Description of problem:
> > > 
> > > I was wondering why changes in /etc/sysconfig/autofs, and in particular
> > > seting OPTIONS there, have no effect in a startup.  After looking closer
> > > at /etc/init.d/autofs  I found that this does
> > 
> > As it turns out this is the only option that is effected by this
> > as the config is read by the daemon itself at startup, except for
> > the OPTIONS variable which is meant for the init script only.
> > 
> > Oops.
> > 
> > I'll change the test in the init script straight away.
> > 
> 
> Done.
> Look for a new version of autofs autofs-5.0.0_beta4-1.

Fixed in autofs-5.0.0_beta4-1.