Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Sat, 25 Dec 2004 19:37:10 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: chmod on named pipes
Message-ID: <20041226003710.GA3027@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20041226002836 DOT GQ18385 AT OCF DOT Berkeley DOT EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041226002836.GQ18385@OCF.Berkeley.EDU>
User-Agent: Mutt/1.4.1i

On Sat, Dec 25, 2004 at 04:28:36PM -0800, Jeremy Lin wrote:
>Hi,
>
>I'm trying to get a program running on Cygwin, but this program depends
>on being able to change permissions on a named pipe. chmod doesn't
>actually seem to work for this, but it doesn't return nonzero either.
>
>From what I can see, the mode argument in the initial mkfifo call is
>respected, but I can't actually change the mode after it's been created.
>
>Is this a known limitation, or am I missing something? I also tried
>looking at the cygwin dll source to see how chmod is implemented, but
>haven't had much luck finding the right spot as of yet (if it's even in
>that particular package), so any pointers there would be appreciated.

fgrep chmod *.cc

seems to do a wonderful job finding several likely suspects for where
chmod would be implemented.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/