From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roger Pau Monne Subject: Re: [PATCH 9/9] init/NetBSD: move xenbackendd to xend init script Date: Wed, 18 Jul 2012 12:02:10 +0100 Message-ID: <500697B2.7020306@citrix.com> References: <1342002232-75531-1-git-send-email-roger.pau@citrix.com> <1342002232-75531-10-git-send-email-roger.pau@citrix.com> <20485.36379.841767.872741@mariner.uk.xensource.com> <50059187.8080802@citrix.com> <50067C0D.9020908@amd.com> <20486.38117.749305.522423@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20486.38117.749305.522423@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Christoph Egger , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org Ian Jackson wrote: > Christoph Egger writes ("Re: [PATCH 9/9] init/NetBSD: move xenbackendd to xend init script"): >> On 07/17/12 18:23, Roger Pau Monne wrote: >>> Yes, but xend seems to spawn two processes that regenerate, so you have >>> to kill them with one shot, or it will be useless. "xend stop" doesn't >>> work either, but since xend is deprecated I think it's rather useless to >>> try to fix this properly now. >> pkill xend should do it. :) > > What if some other thing on the system has a process called `xend' ? > Does it limit it to processes owned by root or something ? > > Or is it just expected that on *BSD we will occasionally kill the > wrong process ? I'm using the full path (pkill -f /usr/xen42/sbin/xend), so unless another process has an argument that's /usr/xen42/sbin/xend (which I've never seen) it will only kill xend.