Date: Sat, 31 Jan 1998 15:56:52 -0500 From: Matthew Hunt <mph@pobox.com> To: Julian Elischer <julian@whistle.com>, hackers@FreeBSD.ORG Subject: Re: cvSup and permissions Message-ID: <19980131155652.02149@mph124.rh.psu.edu> In-Reply-To: <Pine.BSF.3.95.980131114918.13409A-100000@current1.whistle.com>; from Julian Elischer on Sat, Jan 31, 1998 at 11:58:10AM -0800 References: <Pine.BSF.3.95.980131114918.13409A-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 31, 1998 at 11:58:10AM -0800, Julian Elischer wrote: > Can cvsup be told to 'leave it alone'? > should I set up everyone to some different group? I had this problem when I upgraded my cvsup to 15.2. I run cvsup in checkout mode, so this information might not be quite right if you're maintaining a repository. I wanted everything to be root:wheel, umask 002, mostly so that wheel could build ports and just su for the install. When I upgraded cvsup, it reset the permissions every time, and filled my logs with "SetAttr" notices. The man page revealed, though, that it honors umask, so I now run it as (umask 002; cvsup -gL3 my.supfile) and all is well. I don't know what it does about ownership, though. Since I run it as root, everything gets root:wheel. Perhaps the normal BSD rules apply, and files are created with the group of the parent? -- Matthew Hunt <mph@pobox.com> * Think locally, act globally. http://mph124.rh.psu.edu/~mph/pgp.key for PGP public key 0x67203349.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980131155652.02149>