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
9 Replies
748 Views