[kepler-dev] noticing strange behavior with SRB Proxy actor
unni.pillai at nyu.edu
Wed Jun 20 13:33:13 PDT 2007
Yes I'm able to Sget the files as Bowner, and NYUIngestMgr and Sls -C
shows that all three have all permissions on the file.
Ok it looks like I was using Schmod -r a(ALL) to imply all
permissions whereas I should have changed owner using Schmod o flag
I did that and can verify Sget using Aowner, Bowner and NYUIngestMgr
and the owner according to Sls -C is correctly shown as Bowner, but
Kepler actor is still returning old files not the new changed file.
On Jun 20, 2007, at 3:10 PM, Arcot Rajasekar wrote:
> Hi Unni
> Are you able to Sget the files as Aowner, Bowner and
> NYUIngestMgr. Smv just changes the logical location of the file
> to a new collection-path does not change any access permissions....
> Check with Sls -C. Schmod allows you to modify access as well as
> On Wed, 20 Jun 2007, Unni Pillai wrote:
>> Hi Folks
>> Background: In my SRB managed collections, I have couple of
>> different collections and srb accounts. I've an account called
>> NYUIngestMgr which has all access permissions on two separate
>> collections (A & B).
>> Collection A & B are owned by their respective users Aowner and
>> Bowner. NYUIngestMgr has all access to both collections. Using
>> NYUIngestMgr account I moved(Smv) file from collection A to
>> collection B.
>> Now when one of my colleagues uses previously working kepler workflow
>> to do a simple get of files in collection B, he/she receives all
>> files except the newly moved file. The kepler workflow is executed
>> by SRB user Bowner on Collection B.
>> Also noticing wackiness when I reconfigure the workflow to use
>> NYUIngestMgr, the workflow fails miserably stating that NYUIngestmgr
>> has permissions problem despite successfully downloading file from
>> CollectionB using Sget with both NYUIngestmgr and Bowner.
>> Cursory examination reveals the file to be owned by collection A
>> still when I run Sls -al on CollectionB as Bowner.
>> Is there a Scommand to change owner, so my kepler workflow continues
>> working as before.
>> P.S. not sure If this needs to be cross-posted to srb-chat
>> Kepler-dev mailing list
>> Kepler-dev at ecoinformatics.org
More information about the Kepler-dev