> > > > It can't be done atomically, because the ptserver only > provides interfaces > > to add or remove a single group membership for a single > user at a time. > > > > Why does it belong in 'pts', instead of in a script? > > yes that's true , and this is our problem, we have to fork a > binary , authenticate, .... for each add or remove. > this takes to long in a script and we have run time problems > updating a big number of changes in a bulk within a given time. > i think this is a function which makes live easier for admins > in a big environment
At one point, I started work on adding a new RX call that would allow bulk setting of pts memberships/etc., but never had enough priority to go further on it, and now that we're moving away from AFS (not my choice), it's likely I'll never do much withit. I think at one point I put in a request for a new opcode, but never got any further. That would be the way I would recommend making this change - get a bulk operation call implemented so it can be done efficiently and atomicly. -- Nathan _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
