[bind10-dev] component shutdown should handle hanging process

[Michal 'vorner' Vaner]

Hello

On Thu, Oct 25, 2012 at 09:47:35AM -0700, JINMEI Tatuya / 神明達哉 wrote:
> At Thu, 25 Oct 2012 09:56:17 -0500 (CDT),
> "Jeremy C. Reed" <jreed at isc.org> wrote:
> > 
> > My b10-auth is hung:
> > 
> > > Auth shutdown
> > {
> >     "error": "Module 'Auth' not responding"
> > }
> > 
> > So it can't get the "shutdown" command sent to it (via msgq).
> > 
> > Should boss then try to kill it?
> > 
> > or should we have something like the following?
> > 
> > Boss shutdown FOO
> 
> I think this (Boss) approach is more reasonable.

I don't know. I think we have two separate problems here. Or maybe three. It
would be nice to solve them all, of course, but were low priority until now.
 • The <component> shutdown should really be hidden. This is internal command
   and is not expected to by called by user (partly because it doesn't do what
   one would expect, since the component gets restarted immediately).
 • There's no way to „disable“ a component in boss. It can be only removed from
   the configuration, with all the settings on how to start it.
 • If the boss wants to shut down a component and it is stuck, it just fails to
   do so and gets stuck in the state where it is trying to shut it down for
   ever.

Of course, we should never have anything stuck in the first place O:-)

With regards

-- 
No, I will not change your lightbulb.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20121025/e1a2b8f1/attachment.bin>