From owner-freebsd-current  Fri Dec 25 20:52:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA01341
          for freebsd-current-outgoing; Fri, 25 Dec 1998 20:52:34 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01336
          for <current@FreeBSD.ORG>; Fri, 25 Dec 1998 20:52:31 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA17319;
	Sat, 26 Dec 1998 15:52:15 +1100
Date: Sat, 26 Dec 1998 15:52:15 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199812260452.PAA17319@godzilla.zeta.org.au>
To: bde@zeta.org.au, green@unixhelp.org
Subject: Re: revoke of fifos
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> >revoke(2) on VFIFO types is broken now, leading to stranded mbuf's. I suppose
>> 
>> I don't think it has ever worked in BSD.
>
>Nor should it need to since, according to revoke.2:
>     Access to a file may be revoked only by its owner or the super user.  The
>     revoke() function is currently supported only for block and character
>     special device files.

The restriction to special files was removed in Lite2, but the man page was
not updated and revoke on fifos didn't actually work.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message