Re: [Xen-devel] [PATCH] Fix xend restarting problem on NetBSD

[Roger Pau Monné <roger.pau@xxxxxxxxxxxxx>]

While searching for a man page to show you the check_pidfile options
I've found that you can also set a variable with the path to the
interpreter, so no need to expand the script. The only strange thing
is that I have to use SIGKILL to kill xend, SIGTERM seems to do
nothing (also xend spawns two processes, but I guess this is normal).

Attached an updated patch, with a simpler script.

Thanks for making me look at it again, Roger.

2011/7/15 Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>:
> Roger Pau Monné writes ("[Xen-devel] [PATCH] Fix xend restarting problem on 
> NetBSD"):
>> This patch fixes a problem with xend restart on NetBSD
>
> Hi.  Thanks for the patch.  But I think this patch does more than you
> say it does ?
>
> It introduces a new xen_startcmd, xen_stop and xen_status.  Presumably
> these were previously provided by standard NetBSD machinery ?  Why is
> that standard machinery unsuitable for start and status ?
>
>> (the rc.d script was unable to find the pid of the process, so it
>> was not restarted).
>
> Why wasn't the standard NetBSD machinery able to find the pid ?
> How does its approach differ from check_pidfile ?
>
> Sorry if these are all stupid questions.  If you can refer me to some
> documentation about the NetBSD init system I may be able to pretend to
> be less ignorant :-).
>
> Thanks,
> Ian.
>

patch-xend-rc
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel