RE: Bad files perms
No, there's no reason to reset SGID on all the repository directories. You would only need to set it for the newly created subdirectory with something like: chmod g+s new-subdir Read more about loginfo scripts to see how you can write such a script. Noel --- GOMEZ Henri <[EMAIL PROTECTED]> wrote: > >Initially, directories within the repo don't have > SGID > >set. You'll have to do this manually. > > And each time at commit time via loginfo like this ? > : > > # loginfo > # > > DEFAULT find $CVSROOT -type d | xargs chmod g+s __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Bad files perms
>Initially, directories within the repo don't have SGID >set. You'll have to do this manually. And each time at commit time via loginfo like this ? : # loginfo # DEFAULT find $CVSROOT -type d | xargs chmod g+s ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Bad files perms
Initially, directories within the repo don't have SGID set. You'll have to do this manually. Noel --- GOMEZ Henri <[EMAIL PROTECTED]> wrote: > >Initially: > >find $CVSROOT -type d | xargs chmod g+s > > > >I forget whether SGID is inherited by new > >subdirectories. If not, have a loginfo script set > it. > > What do you means by Initially ? > > --- > > loginfo > > DEFAULT find $CVSROOT -type d | xargs chmod g+s > > > > Thanks > > PS: Did you do a 24/24 - 7/7 hot line ? Better than > commercial companies > > > >Noel > >--- GOMEZ Henri <[EMAIL PROTECTED]> wrote: > >> >> The problem is that each time a cvs user like > bob > >> commit > >> >> a file or directory, like test in prj1, > >> >> the file is bob:bob instead of bob:cvsusers > >> > > >> >You need to set the SGID bit on all the > repository > >> directories (chmod > >> >g+s). That causes newly created files and > >> directories to get their > >> >group ownership from their parent directory > rather > >> than from the > >> >creating process. > >> > >> Did there is an easy way to propagate the SGID > bit > >> to sub-dirs ? > >> > >> ie: > >> > >> /home/cvsroot/testproj is owned by bob:cvsusers > with > >> SGID bit set > >> > >> linda commit test.java > >> > >> /home/cvsroot/testproj/test.java will be owned by > >> linda:cvsusers > >> > >> now linda create a subdir packa > >> > >> /home/cvsroot/testproj/packa is owned by > linda:linda > >> ! > >> > >> Thanks for your expertise here also :) > >> > >> BTW: May be there is post-commit hack which could > be > >> used ? > >> > >> > >> > >> > >> > >> > >> ___ > >> Info-cvs mailing list > >> [EMAIL PROTECTED] > >> http://mail.gnu.org/mailman/listinfo/info-cvs > > > > > >__ > >Do You Yahoo!? > >Great stuff seeking new owners in Yahoo! Auctions! > >http://auctions.yahoo.com > > __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Bad files perms
>Initially: >find $CVSROOT -type d | xargs chmod g+s > >I forget whether SGID is inherited by new >subdirectories. If not, have a loginfo script set it. What do you means by Initially ? --- loginfo DEFAULT find $CVSROOT -type d | xargs chmod g+s Thanks PS: Did you do a 24/24 - 7/7 hot line ? Better than commercial companies > >Noel >--- GOMEZ Henri <[EMAIL PROTECTED]> wrote: >> >> The problem is that each time a cvs user like bob >> commit >> >> a file or directory, like test in prj1, >> >> the file is bob:bob instead of bob:cvsusers >> > >> >You need to set the SGID bit on all the repository >> directories (chmod >> >g+s). That causes newly created files and >> directories to get their >> >group ownership from their parent directory rather >> than from the >> >creating process. >> >> Did there is an easy way to propagate the SGID bit >> to sub-dirs ? >> >> ie: >> >> /home/cvsroot/testproj is owned by bob:cvsusers with >> SGID bit set >> >> linda commit test.java >> >> /home/cvsroot/testproj/test.java will be owned by >> linda:cvsusers >> >> now linda create a subdir packa >> >> /home/cvsroot/testproj/packa is owned by linda:linda >> ! >> >> Thanks for your expertise here also :) >> >> BTW: May be there is post-commit hack which could be >> used ? >> >> >> >> >> >> >> ___ >> Info-cvs mailing list >> [EMAIL PROTECTED] >> http://mail.gnu.org/mailman/listinfo/info-cvs > > >__ >Do You Yahoo!? >Great stuff seeking new owners in Yahoo! Auctions! >http://auctions.yahoo.com > ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Bad files perms
Initially: find $CVSROOT -type d | xargs chmod g+s I forget whether SGID is inherited by new subdirectories. If not, have a loginfo script set it. Noel --- GOMEZ Henri <[EMAIL PROTECTED]> wrote: > >> The problem is that each time a cvs user like bob > commit > >> a file or directory, like test in prj1, > >> the file is bob:bob instead of bob:cvsusers > > > >You need to set the SGID bit on all the repository > directories (chmod > >g+s). That causes newly created files and > directories to get their > >group ownership from their parent directory rather > than from the > >creating process. > > Did there is an easy way to propagate the SGID bit > to sub-dirs ? > > ie: > > /home/cvsroot/testproj is owned by bob:cvsusers with > SGID bit set > > linda commit test.java > > /home/cvsroot/testproj/test.java will be owned by > linda:cvsusers > > now linda create a subdir packa > > /home/cvsroot/testproj/packa is owned by linda:linda > ! > > Thanks for your expertise here also :) > > BTW: May be there is post-commit hack which could be > used ? > > > > > > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs __ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Bad files perms
>> The problem is that each time a cvs user like bob commit >> a file or directory, like test in prj1, >> the file is bob:bob instead of bob:cvsusers > >You need to set the SGID bit on all the repository directories (chmod >g+s). That causes newly created files and directories to get their >group ownership from their parent directory rather than from the >creating process. Did there is an easy way to propagate the SGID bit to sub-dirs ? ie: /home/cvsroot/testproj is owned by bob:cvsusers with SGID bit set linda commit test.java /home/cvsroot/testproj/test.java will be owned by linda:cvsusers now linda create a subdir packa /home/cvsroot/testproj/packa is owned by linda:linda ! Thanks for your expertise here also :) BTW: May be there is post-commit hack which could be used ? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Bad files perms
GOMEZ Henri writes: > > The problem is that each time a cvs user like bob commit > a file or directory, like test in prj1, > the file is bob:bob instead of bob:cvsusers You need to set the SGID bit on all the repository directories (chmod g+s). That causes newly created files and directories to get their group ownership from their parent directory rather than from the creating process. -Larry Jones Hello, local Navy recruitment office? Yes, this is an emergency... -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
