HP3000-L Archives

January 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James B. Byrne" <[log in to unmask]>
Reply To:
James B. Byrne
Date:
Tue, 9 Jan 2001 13:12:23 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (71 lines)
        On 9 Jan 2001, at 17:57, Lars Appel wrote:

> James,
>
> as others on HP3000-L already pointed out... SYSINFO version
> A.04.00 seems to work better... Same for me, my system has that
> version and its output shows several class names for my Jetdirect
> LDEVs.

Thanks to all who responded and for the suggested answers
to my original query.  We are scheduled to update from 6.0 to
6.5 shortly so I will have to wait to try this out.

I think that adding a SHOWCLASS CI command would be an
idea worthy of consideration for future releases of MPEiX.

On another topic, a situation with respect to ACDs came up
while I was trying to get SYSINFO to run from a non privileged
user and account.  I would like your comments.

For security reasons the TELESUP account is limited to AC
access across the board.  We do this with every account that
doesn't contain software that absolutely requires a more
lenient security policy.  When I tried to run sysinfo as a non-
privileged use it wouldn't run, obviously.  So I logged on as SM
and ran ALTSEC sysinfo.... ;NEWACD=(X:MANAGER.@)

This doesn't work.  To use @ in the account portion you must
only use @ in the user portion. Why? I am curious why one
cannot use a wild card in the account portion without given all
users access in the user portion. I would have expected that
ACDs would support any form of wild cards such as

@.TEST, or

[log in to unmask]@TEST, or

@USR.TEST@, or

 @[log in to unmask]@T, or

[log in to unmask]

Testing shows that the only allowable combinations are:

@.TEST, and

@[log in to unmask]

Why is this so?  Is there a technical reason for this?

Due to my repeated exposure to HP-UX, which as far as I
know doesn't cause cancer even if it may induce premature
aging, I am growing more and more accustomed to using
regexp.  The effect of this exposure has now reached the point
where I find myself typing LISTF Y*, -1 instead of Y@ on the
HP3000 and wishing that MPEiX would allow * as an alternate
character for @ in file expressions in CI commands.

Actually, what I would really like is for MPEiX to support
regexp at the CI.  I know, heresy!.  What can I say? Mea
Cupa, Mea Cupa, ...

Regards,
Jim
---   *** e-mail is not a secure channel ***
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
mailto:[log in to unmask]  Canada L8E 3C3

ATOM RSS1 RSS2