[656] in Info-AFS_Redistribution

home help back first fref pref prev next nref lref last post

Re: is there a way to get a listing of pts group names?

daemon@ATHENA.MIT.EDU (Ted_Anderson@transarc.com)
Wed Mar 11 12:40:51 1992

Date: Wed, 11 Mar 1992 09:57:57 -0500 (EST)
From: Ted_Anderson@transarc.com
To: Info-AFS@transarc.com, paulinel@ajones.austin.ibm.com
Cc: bob@ibmpa.awdpa.ibm.com (Bob Andrews), dstokes@sunlight.austin.ibm.com,

Before people get carried away with these moderately horrible shell
scripts let me second Bob Andrews' suggestion of using testpt.  I never
installed this program for two reasons: (1) I was worried about server
load, and (2) I couldn't think of a reasonable name.  Clearly (2) is
minor.  Reason (1), however, looks like it will be a feature at this
rate.  Because it makes calls to the ptserver using the bulk id-to-name
RPC, it will be *far* more efficient that the scripts described so far. 
The potential for abuse still exists, since in a large cell it will make
hundreds of moderately heavyweight (although cheaper than *any* update
operation) calls in a short period of time.

As for restricting the access to system:administrators, this clearly
isn't going to work.  Because the basic functions used by "pts examine"
isn't controlled, there is no real way to prevent server overload by
restricting this operation.

In conclusion you should certainly use testpt before running one of
these shell scripts.

I realize that because testpt is not installed it is not part of the
binary release.  Consequently, binary-only customers will not have
access to this command.  This is unfortunate but I guess the shell
scripts are the best bet for those folks.

Ted

home help back first fref pref prev next nref lref last post