/etc/init.d in the default $PATH ?

[Jerry Williams]

> -----Original Message-----
> From: fedora-devel-list-bounces at redhat.com [mailto:fedora-devel-list-
> bounces at redhat.com] On Behalf Of Konstantin Ryabitsev
> Sent: Sunday, January 28, 2007 7:30 PM
> To: Development discussions related to Fedora Core
> Subject: Re: /etc/init.d in the default $PATH ?
> 
> On 1/28/07, Rex Dieter <rdieter at math.unl.edu> wrote:
> > > OTOH, if all files in /etc/init.d would be named init-<service-name>
> or
> > > something like that, then the ambiguity would disappear and the
> > > /etc/init.d could be added to the default $PATH.
> >
> > Or just use:
> > # service <service-name>
> 
> Yes, and bash-completion *will* tab-complete the entries from
> /etc/init.d for you when you use "service".
> 
> Cheers,
> --
> Konstantin Ryabitsev
> Montréal, Québec

That is interesting.
cd /etc/init.d
service wi<TAB> works
Doesn't seem to matter if /etc/init.d is in the PATH or not.
If you aren't in /etc/init.d service wi<TAB> doesn't work even if
/etc/init.d is in your PATH.

I don’t' think that /etc/init.d should be in your path.
Either use the service command or cd /etc/init.d and use ./command.
Or /etc/init.d/command.

I seem to always cd to /etc/init.d to look most of the time I can't remember
the name of a service anyway.