Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <011201c0b6ae$c3f7de20$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
Subject: whats a good magic number for fifo's?
Date: Tue, 27 Mar 2001 21:12:06 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 27 Mar 2001 11:06:56.0185 (UTC) FILETIME=[093BC290:01C0B6AE]

The title says it all.

I'm extending the magic number checks in fhandler_base... this will have
a performance impact (the assume exe flag and/or ntsec will no longer
shortcut the file open and read tests). I'm open to suggestions for
marking the file as a fifo without magic numbers.

For the moment I will optimise the test by only checking files that are
the right number of bytes long. That should keep things fairly smooth
for most users.

I don't consider the registry a valid option (just imagine the support
requests "we run off a NFS share, we created a fifo, but it's not
recognised .. why not????" ) - but a CYGWIN flag to switch between
registry or magic numbers might work.

Rob