From owner-freebsd-bugs  Fri Mar 23 15:36: 2 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8CA1537B719; Fri, 23 Mar 2001 15:36:00 -0800 (PST)
	(envelope-from mpp@FreeBSD.org)
Received: (from mpp@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f2NNZxF49499;
	Fri, 23 Mar 2001 15:35:59 -0800 (PST)
	(envelope-from mpp)
Date: Fri, 23 Mar 2001 15:35:59 -0800 (PST)
From: <mpp@FreeBSD.org>
Message-Id: <200103232335.f2NNZxF49499@freefall.freebsd.org>
To: jau@iki.fi, mpp@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/23990: access(2) system call reports an immutable file as writable
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: access(2) system call reports an immutable file as writable

State-Changed-From-To: open->closed
State-Changed-By: mpp
State-Changed-When: Fri Mar 23 15:25:52 PST 2001
State-Changed-Why: 
I've verified that the access(2) system call returns the correct value
when testing if immutable files can be written.  I tested on 4.0, 
4.2-stable, and 5.0-current.  

I think you may not have been confused about how the "access" command 
was working (the one I've got on my system was installed as part of the 
teTeX port).  It appears to just be a very stripped down version of
the "test" command.  Here is output from a session:

Script started on Fri Mar 23 17:19:33 2001
acme 1%	touch testfile
acme 2%	access -w testfile
acme 3%	echo $status
0
acme 4%	chflags uchg testfile
acme 5%	access -w testfile
acme 6%	echo $status
1
acme 7%	exit
exit

Script done on Fri Mar 23 17:20:04 2001

Note that the command doesn't output any messages if access to the
file is not allowed.

http://www.freebsd.org/cgi/query-pr.cgi?pr=23990

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