From mboxrd@z Thu Jan 1 00:00:00 1970 From: Muli Ben-Yehuda Subject: Re: [PATCH] [RFC] Domain name issue Date: Sun, 18 Jun 2006 12:29:32 +0300 Message-ID: <20060618092932.GD5892@rhun.ibm.com> References: <0C692B8F40423kanno.masaki@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <0C692B8F40423kanno.masaki@jp.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Masaki Kanno Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sun, Jun 18, 2006 at 06:24:09PM +0900, Masaki Kanno wrote: Content-Description: Mail message body > Hi, > > When we tested xm commands, we found a issue about a domain name. > The domain name can use character '-'. However, when character '-' > was used for the top of the domain name character string, the > following issue was found. > > # xm list > Name ID Mem(MiB) VCPUs State Time(s) > -domUtemp 1 512 1 r----- 43.2 > Domain-0 0 492 1 r----- 199.2 > # xm list -domUtemp > Error: option -d not recognized > > Some xm commands mistook such the domain name for a option. > We suggest the following patch. The patch changes XendDomainInfo.py > not to be able to use character '-' for the top of the domain name > character string. The standard way of handling this is to add '--' on the command line to tell the program that everything that follows is an argument, not an option. I don't know if xm supports this however. The above command line would then become xm list -- -domUtemp Does this work? Cheers, Muli