Date: Tue, 20 Oct 1998 19:03:04 -0700 From: John Polstra <jdp@polstra.com> To: Christopher Masto <chris@netmonger.net> Cc: current@FreeBSD.ORG Subject: Re: cvsup and file permissions Message-ID: <199810210203.TAA07982@austin.polstra.com> In-Reply-To: Your message of "Tue, 20 Oct 1998 21:56:09 EDT." <19981020215609.A20479@netmonger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> How right you are. Ouch. The problem is that I've been using sudo
> to run it, and while I've been setting _my_ umask to 2 for years,
> I see that it is not being inherited when I sudo. I feel like an
> idiot and I apologize for wasting your time.
No need. I'm just glad the problem is solved. You're not the first
person to run into something like this. It reinforces the need for
CVSup to support a "umask" specification in the cvsupfile itself.
The only problem is, it's not as simple as it sounds. The user might
reasonably want to specify different umask values for different
collections. But CVSup can't simply use those values to call umask()
directly, because at any given time it may well be working on up
to 3 collections simultaneously. (That's because of its pipelined
architecture.) So the effects of the umask system call will probably
have to be faked manually, and that's why I haven't implemented it
yet.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810210203.TAA07982>