This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Create file fails on network drives in cygwin-1.7.9-1

On Jun 17 09:34, Pete Forman wrote:
> On 16 June 2011 15:58, Corinna Vinschen wrote:
> > Thanks. ÂAFAICS the permissions on that network drive don't allow a
> > user to set the ACL of a file he or she's just creating. ÂIn contrast
> > to previous versions, Cygwin 1.7.9 requests the permission for that
> > right at file creation time. ÂUnfortunately that fails due to the
> > weird permission settings on that drive.
> >
> > Try to mount your drive with the noacl option to some arbitrary mount
> > point, for instance:
> >
> > Âmount -f -o noacl,binary X: /my_x_drive
> >
> > and then use the path below that mount point to access the drive.
> >
> > If that works, you can add the path to your personal fstab
> > file (see
> >
> > ÂX: /my_x_drive none noacl,binary,posix=0 0 0
> >
> > Please report back if it helped. ÂIf so, I'll add some workaround for
> > this problem to the next Cygwin version.
> My first couple of goes did not work reusing the /cygdrive mount
> point. What did work was using /my_t as a mount point.

Yes, that's what I wrote above.

  "and then use the path below that mount point to access the drive"

> ## turn off acl
> $ mount -f -o noacl,binary H: /cygdrive/h

That's not what I wrote above.  You can't override the mode of a single
cygdrive path.  All cygdrive paths are subsumed under a single cygdrive
mount entry.

> ## switch off case sensitivity
> $ mount -f -o noacl,binary,posix=0 H: /cygdrive/h

posix=0 is default for the cygdrive prefix anyway.  That's also not
what this issue is about.

> $ mount -f -o noacl,binary T: /my_t

Yes, that's what I wrote.

> $ mount -f -o noacl,binary T: /cygdrive/t

This, again, obviously can't work.

> $ cd /my_t/Pete\ F
> $ rm foo.txt
> $ touch foo.txt

Yes, that's what I expected.  That's the workaround of choice.

Btw., it would be an incredible good idea to change the permissions on
the remote drive to allow users to set or change the permissions of
files they created themselves.  Otherwise you end up with non-POSIX
permissions on the drive anyway, whether or not you're using "acl" or
"noacl" mount option.  If the network drives are not under your control,
try to persuade the admin.  If the admin is adamant, use the noacl mount
option for these drives.  You can also just change the cygdrive prefix
to use noacl on all drives.  See the User's Guide for how to do it.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]