I'm talking about not being able to hit "a" and have it jump to the
first entry starting with an "a" in the "Clients"/"Groups"/"Index"
windows of the 7.1.3 windows GUI.  This is a lame bug... has anyone
reported it to Legato?  I'm a Sun user, so I'm not sure how effective my
complaints will be.

Did anyone test this interface before it was released?!?!  Such an
obvious bug!!!

Joel

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Tim Mooney
Sent: Tuesday, April 05, 2005 12:01 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] context searching in 7.1.3 nwadmin

In regard to: Re: [Networker] context searching in 7.1.3 nwadmin,
Davina...:

> Manel Rodero wrote:
>> Hi,
>>
>> We're now with 7.1.2 and the problem is here too. Is a new "feature"
;-) Is
>> like the problem existent with machines with similar names and the
searching
>> that Legato does. Example:
>>
>> client1.domain
>> controlclient1.domain
>>
>> If you no a 'nsradmin' to update only 'client1.domain' the update
will
>> affect to 'controlclient1.domain' because its right part is the same.
:-(
>> Very annonying but ... until Legato solves it ...
>
> It's poor coding and really a novice programming error. All that's
> required to get this right is the correct regular expression using a ^
> at the beginning and a $ at the end. An elementary error like this
> shouldn't get through the code review process.

I'm confused.  The "searching for a client" feature the original poster
mentioned sounds like a new bug, but the the behavior described by Manel
above is nothing new or even unexpected -- Legato documents it (though
not
boldly) in the man page for nsradmin:

        3) Values in a query may be in the form of ed(1) style regular
expres-
        sions.   A  pattern match is attempted against all resources
that con-
        tain the specified attribute.

If I'm understanding what you're both talking about above, this behavior
isn't new.  It may be a surpise to NetWorker beginners, but certainly
not
to you, Davina?  Darren Dunham and others have mentioned it on the list
before.  I admit that I sometimes forget that nsradmin uses *unanchored*
basic regexes, but it only takes one query to remind me again that I
have
to anchor my own queries.

Am I completely misunderstanding what's being discussed?

Tim
-- 
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=