From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaun Reitan Subject: Re: [PATCH] for xend init script and xend python script Date: Fri, 29 Oct 2010 10:57:22 -0700 Message-ID: <4CCB0B02.80706@unix-scripts.com> References: <19655.13.392293.144506@mariner.uk.xensource.com> <4CC71222.2070203@unix-scripts.com> <19656.20481.596734.306544@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19656.20481.596734.306544@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 10/27/2010 9:14 AM, Ian Jackson wrote: > ShaunR writes ("[Xen-devel] Re: [PATCH] for xend init script and xend python script"): >> I see in the new xencommons that there's a XENCONSOLED_ARGS env which >> could hold all this info and be set in /etc/sysconfig/xencommons but I'm >> worried about it being overwritten by some of the checks in the script. > > Oh, yes. It would be better if the xencommons script prepended to the > ARGS (so that settings in the /etc/default file can override) rather > than unconditionally setting, or if we had two variables. > >> Either way works i guess, i like separate options because i think it's >> easier for people to write automated scripts against to ensure the >> options they want are enabled. > > Yes. I'd be happy to take a patch to implement separate options in > xencommons in unstable. > > Ian. Ian, I'll go ahead and implement this and submit a patch, i'm alittle busy this week. How long do you think i have until unstable is merged? I would like to make sure this this patch included into the next version so trying to figure out my time line :) -- Shaun Retian Chief Technical Officer Network Data Center Host, Inc. http://www.NDCHost.com