Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#392370: rsync (Cygwin) can't overwrite read-only files on Samba share

0 views
Skip to first unread message

Harald Dunkel

unread,
Oct 11, 2006, 11:10:09 AM10/11/06
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: samba
Version: 3.0.14a-3sarge2

To reproduce, export your home using samba

[homes]
read only = no
create mask = 0644
directory mask = 0755
browseable = no
guest ok = yes

Mount this share on a Windows host (XP, Cygwin), enter
bash and switch to this directory. Next run

touch x y
chmod -w y
rsync x y

I got an error message saying

rsync: rename "/cygdrive/x/fuerharri/.y.KTKKRo" -> "y": Permission denied (13)
rsync error: some files could not be transferred (code 23) at /home/lapo/packaging/tmp/rsync-2.6.6/main.c(791)

If I use Unstable's Samba to share a disk, then there is
no such problem. There is no such problem with Samba on
RedHat EL3 or 4, either.


Regards

Harri

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFLQH0UTlbRTxpHjcRAvoqAJ9FRlO3xH8OEFDj8aOi9JazeF0VAQCdEprt
oMIvlW7FJYPWAj9esPymSxU=
=PIpv
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Christian Perrier

unread,
Oct 12, 2006, 3:30:07 AM10/12/06
to
Harald Dunkel a écrit :

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>

>Sorry, but this doesn't help. For running our major server
>I need a fix for Sarge. An upgrade to Testing or Unstable
>is not possible.
>
>It would be very nice to increase the priority of this pr.
>I already get a lot of pressure that I dared to install
>an "evil" Linux on our major server instead of RedHat. This
>bug makes it much more difficult to argue against an
>"upgrade" to RHEL4.
>
>
>
>
Sure, but the policy for handling updates in Debian does not give any
solution. The issue is not a release critical issue but "only" a bug
that has been fixed in later versions of samba.

You're reaching the limits of using Debian stable for your server.

I suggest you try using backports from www.backports.org. They are often
derived from the testing/unstable packages and thus give you some kind
of quality guarantee.

This, of course, waiting for the soon-to-come etch release which will
allow you to switch back to official packages.

If you experience crashes after the upgrade, please check the "passdb
backend" line in smb.conf. It may contain "passdb backend = tdbsam,". In
that case, remove the extra comma.

0 new messages