[scribus] collecting for output
mheieis at alois.ca
Thu Dec 5 20:18:43 UTC 2013
If I understand the issue, think an easier approach would the following:
1) Create a group (e.g. "editors")
2) add the group "editors" to each user id that's working on the group
3) change the group id of the common directory,"pour_la_sortie", to
"editors" (#chgrp -R editors "pour_la_sortie")
4) change the write permissions of the common directory to allow group
writing (#chmod -R g+w "pour_la_sortie")
5) change the group sticky-bit, which keeps the group id to "editors"
(#chmod g+s "pour_la_sortie")
6) any logged in user in the editors group will need to log out if
signed in to see the change
7) you will need to be root or have root access to make the above changes.
8) you only have to do this once as an adminstrator. The rest becomes
totally transparent to the users, with no training overhead
It's also assuming that the common directory is in a location that all
of the users can see and get to.
Hope the helps.
On 2013-12-05 10:03, John Jason Jordan wrote:
> On Thu, 05 Dec 2013 12:26:44 -0500
> Gregory Pittman <gpittman at iglou.com> dijo:
>> On 12/05/2013 12:02 PM, ZASKE Martin wrote:
>>> Each user is working in his own /home folder and we keep all our
>>> work in a folder called "pour_la_sortie" which is French for
>>> Now the idea is that we keep a paper-list on the wall next to the
>>> main layout computer (two full HD screens), of who was the last user
>>> to work on the magazine.
>>> Then the next user will log in and just copy the entire folder into
>>> his /home folder to continue working on those pages, where he or she
>>> is in charge.
>>> BUT: My wife just discovered that she cannot do that. Scribus had
>>> done a nice and complete collecting-for-output. But somehow the
>>> user-rights got assigned such that only scribus-files are accessible.
>>> But all fonts and all illustrations are blocked for "group" and
>>> "others", not even reading is allowed (and reading is all the next
>>> user would need to copy the complete folder with content). This is
>>> something that Scribus must have done during the
>>> collecting-for-output of the previous user, since that user had
>>> started with a blank document I believe.
>> I don't think Scribus has any capability of doing this on its own.
>> Probably something with the OS, maybe someone saved to a subfolder
>> where the parent folder has limited permissions. This is one of those
>> instances where knowing a simple command line command like chmod
>> quickly takes care of this. There should also be some GUI way of doing
>> this with a file manager.
> Each user could have a bash script to change ownership to themselves,
> except that they would probably need the root password to execute it.
> As Gregory noted, the command to change ownership would be chmod,
> although you'd want to make it recursive (the folder and all
> subfolders). The script would be something like:
> sudo chmod -R groupname:username /path/pour_la_sortie
> Where 'sudo' will require the root password before executing the
> command, '-r' means recursive, groupname and username are the user's
> login name and the group to which they belong, and 'path' is the path
> to the folder from the user's computer.
> To create the script copy the above and paste into a plain text editor,
> adjust the command as needed, and save in the user's home folder.
> Select the file in your file browser, right click on it, and select
> Properties. In the Properties window check the box to make it
> executable. Then the user can just double-click on the filename to run
> the script, or you can make a launch icon in the user's Applications
> menu. You can even assign a hotkey combination to it.
> You will have to create a different script for each user because their
> user and group names will be unique.
> Scribus Mailing List: scribus at lists.scribus.net
> Edit your options or unsubscribe:
> See also:
More information about the scribus