This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: When acl() returns -1
On Jun 27 11:56, Igor Pechtchanski wrote:
> On Mon, 27 Jun 2005, Corinna Vinschen wrote:
>
> > On Jun 27 15:40, Dave Korn wrote:
> > > >From: Corinna Vinschen
> > >
> > > > So what's your opinion? Should acl()
> > > >
> > > > keep its behaviour since it's not worth to change it for these files
> > > > which are locked anyway?
> > > >
> > > > or should acl()
> > > >
> > > > return the correct number of faked acl entries which pretend that
> > > > nobody has access to these (locked) files?
> > >
> > > How about keeping acl() the same, and fixing 'ls'?
> >
> > Well... hmm, why not? Sounds good to me, too.
>
> At the risk of sounding trite, me too. :-)
Okay...
> What does Linux do when it finds busy files (I think at least NFS allows
> file locking). Or does that locking not extend to retrieving ACLs?
Linux generally permits to access the file metadata even if the file
is locked, so that's not a problem. Windows has the incredibly annoying
feature that the metadata is part of the file data so locking the file
also locks accessing metadata :-(
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.