<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <a class="moz-txt-link-abbreviated" href="mailto:jam@zoidtechnologies.com">jam@zoidtechnologies.com</a> wrote: <blockquote cite="mid20070128000656.GW3639@zoidtechnologies.com" type="cite"> <pre wrap="">On Sat, Jan 27, 2007 at 04:04:39PM -0800, Florin Andrei wrote: </pre> <blockquote type="cite"> <pre wrap="">So, what it the rationale for /etc/init.d not being in the default $PATH, for root at least?</pre> </blockquote> <pre wrap=""> I've never had to execute anything directly in /etc/init.d/ -- there is the "service" command that runs those files for me, at least in fedora. you can always modify $PATH by dropping a file into /etc/profile.d/ if you *really* want this sort of thing to be possible. I would not want to see it in fedora though. </pre> </blockquote> I'd agree, but it does bring something else to mind. I don't modify the path on my system from the install default, but when logged in as root via 'su', /sbin is not in the path. I do see something in /etc/profile that is apparently supposed to put it in there if the EUID is zero, but it never seems to happen. I hadn't really thought about it much till now. Is that a bug? Does this happen to anyone else? It also happens when using sudo, i.e. "sudo service" gets "sudo: service: command not found", whereas "sudo /sbin/service" shows usage for service. -Ron </body> </html>