> So, it does much what the `su` command does, yes? By default su asks for
> Super-User priviliges, but if you give an account name (exactly what
> you're saying you do with `be`) then you can Switch to that User. What can
> the `be` commad do that `su` can't, out of curiosity?
It's like "su", but "be" actually doesn't refer to actual users; the
projects are file paths linked with a database of users who have
priviledges to read, write, and so on to those file paths. So instead of
having all the usual users AND a few 1000 project users who all share the
same password for the project, we use this "be" utility.
Hence, your idea will not work since I can't ssh to an unknow user.
But... I like this idea which may be useful later on. So THANKS!
However, I think a few of us here have come up with a work-around. The
"be" command can accept options which allow additional programs to be run
without invoking another shell. For example,
user% be proj1 "ls ~/"
user% be proj1 "cd; ls"
Both of these will list the contents of the files in the "proj1" directory
and return an exit code of $? = 0. So I think this will solve the problem
by doing:
$stat = system("be $proj \"$path/convert.pl $file\" ");
where convert.pl will convert $file under the identity of $proj. So it's
just a matter of writing two different programs, or maybe writing the
conversion as a sub-routine.
Thanks,
Chris.
--------------------------------------------------------
Chris Staskewicz
Channing Laboratory - Brigham and Woman's Hospital
tel: 617.525.2575
fax: 617.525.2578
--------------------------------------------------------
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
