On 08/30/14 12:54, JD wrote:
> Thanks Ralph and John, I've put those ideas into practice (manually)
> and everything seems OK. Neil, I already had a new group for all
> (i.e. 2!) users but it is not their primary group. Firstly, do I have
> to edit /etc/passwd to change users' primary group? Secondly, would
> that change and a new standard umask mean that all files are writeable
> to all users?
ok, providing the directory is g+ws, and group users, and the users are
members of the 'users' group (all of which seem to be fulfilled right?)
this system will work (tried it myself to prove it) and the users don't
need to have their primary group changed (huzzah)
>
> I now need to create the cron job. I'm not sure how to do it in a
> situation like this where I need to run the find command with sudo. I
> can't do su, presumably because root doesn't have a password.
>
To be honest, once the 'old' files are in place, and the above criteria
are met, you can just;
find /home/shared -exec chgrp users {} \;
as root and you shoulnd't need any cron jobs...
> Also, since I have an all-users group I guess I could change the find
> from:
>> find /home/shared -type f ! -perm -22 -ls -exec chmod go=u {} +
> to:
> find /home/shared -type f ! -perm -22 -ls -exec chmod g=u {} +
>
> (I deleted an "o"!).
>
> John C-C, thanks for the info on setuid bit on the directories. I
> thought setuid was just for executables.
set GID on directories does EXACTLY what you want here...
>
> Regards,
> John
>
--
Next meeting: Bournemouth, Tuesday, 2014-09-02 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
New thread on mailing list: mailto:dorset@mailman.lug.org.uk
How to Report Bugs Effectively: http://goo.gl/4Xue
