On Mon, 8 May 2017, John Edstrom wrote:
Yeah, but there's also a third permission scheme that I hadn't been properly aware of. There's also the internal user/group SQL permission scheme in the USER_NAME & USER_PERMS tables.
If I uderstand you correctly, you're talking about *Rivendell* users, defined in the 'Rivendell' database, and not MySQL users (defined in the 'mysql' database) or Linux users (defined in /etc/passwd and /etc/shadow).
I was using the imported SQ data on a new machine who's users didn't conform exactly to the old machine's Linux users.
One problem I have encountered is porting a MySQL database from an old version of MySQL to a newer one with a different password length. The MySQL users' passwords all become invalid and have to be re-entered. But I don't think I've ever run into this problem in a Rivendell context.
For example, linux user JohnDoe on the original machine may have rivendell permission to run rivendell tools, but he may be constrained to only manipulate carts of type TALK, NEWS-L and ARTS-N, and not be allowed to see/edit carts of type MACROS, or VOICETRACK, etc., according to the data in the USER_PERMS table.
Here I'm afraid you've lost me. *Linux* user JohnDoe? I've never seen a Rivendell system with more than one non-root, non-system Linux user.
Rob -- Я там, где ребята толковые, Я там, где плакаты "Вперёд", Где песни рабочие новые Страна трудовая поёт.
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
