Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Des Dougan on March 12, 2001, 05:36:46 AM
-
I've successfully applied the named RPM to my 4.1 installation. I assumed that I would need to stop and start named to fully apply the changes. I've looked at the key concepts web page, which indicates that I should run /sbin/e-smith/signal-event xxx. I found in /etc/e-smith/events/actions a file called restart-named, but when I try to run /sbin/e-smith/signal-event restart-named I get this message: Can't open directory /etc/e-smith/events/restart-named. Obviously restart-named is a file (in the actions subdirectory). How do I make it run? I'm obviously missing something - I don't need to run the whole set of actions, do I?
Thanks for any help - this is the first time I've tried to do something different with e-smith. I know in other distributions I could run the change from /etc/rc.d/init.d.
Des Dougan
-
Des Dougan wrote:
>
> I've successfully applied the named RPM to my 4.1
> installation. I assumed that I would need to stop and start
> named to fully apply the changes. I've looked at the key
> concepts web page, which indicates that I should run
> /sbin/e-smith/signal-event xxx. I found in
> /etc/e-smith/events/actions a file called restart-named, but
> when I try to run /sbin/e-smith/signal-event restart-named I
> get this message: Can't open directory
> /etc/e-smith/events/restart-named.
The "events" are stored as links in sibling directories to the
actions directory. Often one action script is used in more
than one event.
> Obviously restart-named is
> a file (in the actions subdirectory). How do I make it run?
> I'm obviously missing something - I don't need to run the
> whole set of actions, do I?
You would normally signal the relevant event which contains
that action script. If you do
ls /etc/e-smith/events/*/*restart-named
you will see that the only times we restart named are when we
modify domains or hosts. We try to restart daemons as
infrequently as possible.
Just run the action script directly:
/etc/e-smith/events/actions/restart-named
> Thanks for any help - this is the first time I've tried to do
> something different with e-smith. I know in other
> distributions I could run the change from /etc/rc.d/init.d.
Ah, but named is not run from an initscript - it is managed by
the "init" daemon. named needs to be running and restarted if
it ever happens to die.
Gordon
-
>> We try to restart daemons as infrequently as possible. <<
But am I correct in assuming that I needed to restart it after applying the RPM?
>> /etc/e-smith/events/actions/restart-named <<
Ran it, but running ps waux | grep named shows it having started yesterday, so does the script not do a stop and a start?
Sorry for the dumb questions...
Des
-
First reply got mangled...
> We try to restart daemons as infrequently as possible.
But am I correct in assuming that I needed to restart it after applying the RPM?
> /etc/e-smith/events/actions/restart-named <<
Ran it, but running ps waux | grep named shows it having started yesterday, so does the script not do a stop and a start?
Sorry for the dumb questions...
Des
-
Des Dougan wrote:
>
> First reply got mangled...
>
> > We try to restart daemons as infrequently as possible.
>
> But am I correct in assuming that I needed to restart it
> after applying the RPM?
Applying which RPM? You mentioned the "named RPM" - but which one, and why?
> > /etc/e-smith/events/actions/restart-named <<
>
> Ran it, but running ps waux | grep named shows it having
> started yesterday, so does the script not do a stop and a
> start?
It does "/usr/sbin/ndc -c /home/dns/var/run/ndc reload".
To restart named, just kill it. Then init will start a replacement automatically.
> Sorry for the dumb questions...
We all know nothing until we learn. And we learn by asking questions and paying attention to the answers.
Charlie
-
Charlie Brady wrote:
>
> Applying which RPM? You mentioned the "named RPM" - but which
> one, and why?
>
Charlie,
The 4.1 upgrade named RPM (e-smith-named-1.4.0-08) - it looks like I will need to use dynamic DNS with this server, as the ISP (Telus) won't give an (advertised) static IP for an ADSL connection (it seems they're short of Class C's). I therefore applied the upgrade as discussed on these forums, but figured that named should be restarted to activate the change.
Thanks again for your help.
Des
-
Des Dougan wrote:
as the
> ISP (Telus) won't give an (advertised) static IP for an ADSL
> connection (it seems they're short of Class C's).
Hi Des, as I know you are in the Vancouver area, if you still need a static ADSL, just give me a call :-)
Regards,
Darrell
-
Des Dougan wrote:
>
> First reply got mangled...
>
> > We try to restart daemons as infrequently as possible.
>
> But am I correct in assuming that I needed to restart it
> after applying the RPM?
To be safe do:
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot
Charlie
-
Charlie Brady wrote:
>
> To be safe do:
>
> /sbin/e-smith/signal-event post-upgrade
> /sbin/e-smith/signal-event reboot
Thanks, Charlie.
Des
-
Darrell,
Thanks, but Telus is a done deal...
Des