From: [EMAIL PROTECTED] (Roland J. Schemers III)
Date: Thu, 23 Sep 1993 13:53:29 -0700
References: <[EMAIL PROTECTED]>
X-Mailer: Z-Mail (2.1.5 09aug93)
On Sep 23, 12:16pm, David Grossman wrote:
>>
> I've done some crude tk/tcl/expect scripts to run emt; nothing worth
> distributing, but I think this is the easiest/fastest way to "customize"
> emt for local use...
>
I think doing something more extensive in TCL/Tk, such as an afssh or
wishafs would be worth while. I had started hacking up something such
that you could do things like:
set acl [afs getacl /afs/blah...]
s
And then the variable acl would contain two lists, something like:
{ {{system:anyuser rl} {system:administrator rlidwka}} {} }
The first list contains a list of positive ACLs, the second list negative.
I wasn't just parsing the output of the fs command, I was making pioctl
calls, etc.
I've also hacked up something called xacl (which does parse the output of
fs :-) that lets you set acl's buy double clicking on them, etc.
I think an AFS shell in TCL/Tk that combined all the functionality of
fs, bos, kas, pts, would be really cool. You could even extend it to
open up a connection to a server that delegated authority, ala adm.
Roland
Actually, I started working on something like this about a little
while ago. I call it afsru, and it will allow delegation of
authority for certain commands. The basic idea is that you write
commands in TCL, and afsru reads that and provides some support
functions. However, since I have found the AFS API manuals pretty
inpenetrable (especially I usually just look in the index), I have not
used any of the RPC calls to servers; instead, I fork off the
appropriate command and parse the output (for example, to find out if
a user is in a particular group I fork off a "pts membership" and read
the output, instead of calling PR_IsAMemberOf).
----------------
Mike Shaddock | Furious activity is no substitute for
UNIX Support | understanding.
[EMAIL PROTECTED] | -- H. H. Williams
(919) 677-8000 x7969 |
----------------
Mike Shaddock | Dimensions will always be expressed in the least
UNIX Support | usable term. Velocity, for example, will be
[EMAIL PROTECTED] | expressed in furlongs per fortnight.
(919) 677-8000 x7969 |
