[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-devel] The Great Renaming(tm) of "vm" => "slot" nowcommitted to HEAD
- Date: Thu, 31 May 2007 11:06:32 -0700
- From: Derek Wright <wright@xxxxxxxxxxx>
- Subject: Re: [Condor-devel] The Great Renaming(tm) of "vm" => "slot" nowcommitted to HEAD
(again, cc'ing my reply to the list, in case others are wondering the
same thing)
On May 31, 2007, at 7:48 AM, Ian Chesal wrote:
I should have thought of this when we were talking in April: but do
you
absolutley need to prefix stuff with 'slot' in the condor_status
view? I
don't see a lot of difference between:
vm1@foo
slot1@foo
-and-
1@foo
Except 1@foo gets me 4 more characters for my hostname in the default
view. :)
a) Ian, meet the STARTD_RESOURCE_PREFIX config knob;
STARTD_RESOURCE_PREFIX, meet Ian, one of your new users.
http://www.cs.wisc.edu/condor/manual/
v6.9.2/3_3Configuration.html#param:StartdResourcePrefix
that said, there's no way to set it to an empty string. :( so, the
best you could do is:
STARTD_RESOURCE_PREFIX = _
# or whatever single char you most prefer, could be 's' or 'vm', etc...
which yields:
_1@foo
...
b) you'll be happy to know that part of my commit changed the widths
of the various columns in the default condor_status view. name now
has 5 more chars, so even with vm => slot, it's still a net gain of 3
more characters of your hostnames. ;) (opsys lost 1, state lost 1,
activity lost 2, and a trailing space was nuked, too).
And thanks for the backwards compatibility with "vm".
for better or for worse, that's how we usually do things around
here. makes everything take longer to develop and harder to maintain
in the code, but at least it's (usually) easier to use.
cheers,
-derek