Subject: Re: startup script buglet
From: Bryan Stillwell (arcane@verinet.com)
Date: Thu Apr 27 2000 - 02:04:02 MDT
> Looks like there's a small bug in the startup scripts.
>
> # cd /etc/rc.d/init.d
> # named restart
> (command fails)
> # ./named restart
> (command works)
>
> the startup scripts assume there's some kind of pathname attached to
> $0. If you're debugging stuff, that might not be true, until you
> figure this out.
The current directory is not usually in your path, so that's why you have
to specify the current directory using ./ before the program name. If you
would like to see what your path is set to you can do a `echo $PATH`.
Also if you modified /etc/named.conf and just wanted to reload the
configuration you should be able to do a `ndc reload`. (ndc should be in
your path, but if it isn't you can run `/usr/sbin/ndc reload`) Restart
actually kills the program and starts it again, so using reload for named
is preferable.
> For general users, they'll never see this. For people whacking on the
> system, it can be confusing and cause problems if they aren't
> careful....
This messed me up when I first started using linux since I was used to the
current directory being considered part of the path in dos, but that's how
it works in Linux and probably most *nixes.
Bryan
This archive was generated by hypermail 2a24 : Thu Apr 27 2000 - 02:03:55 MDT