From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rsyncd broken
Date: Thu, 28 Aug 2014 10:06:00 -0000 [thread overview]
Message-ID: <20140828100611.GR20700@calimero.vinschen.de> (raw)
In-Reply-To: <CAKf2h5RnwkR2=GtdeVy1rQPvjT4pw26L44de4GTB9y=iKriYag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Aug 28 10:22, Frank Fesevur wrote:
> 2014-08-25 9:46 GMT+02:00 Frank Fesevur:
> > 2014-08-22 14:42 GMT+02:00 Frank Fesevur:
> >> I will try a self build vanilla rsync.exe 3.1.1 this weekend or early
> >> next week and see how that works.
> >
> > I have tried my own build 3.1.1 last night and it fails with the same
> > errors. I will investigate this.
>
> Made a bit of progress. When I comment out the lines uid = 0 and gid =
> 0 from my /etc/rsyncd.conf v3.1.1. seems to work again, although I
> haven't tried on our production server yet. I rather wait with that
> until the weekend when there is not much to backup. I have not found
> out why this behavior has changed since v3.0.9.
>
> Another thing that surprises me is that the setuid() fails with an
> errno 5, which is EIO. That error is not mentioned on this man page
> http://linux.die.net/man/2/setuid What do you think? Is this setuid()
> error a cygwin specific problem or should I ask upstream?
That's probably a translation from Windows status or error code to POSIX
error code. The setuid call is littered with debug output statements,
so a strace could help to understand where it comes from. Basically
it's probably still rather an issue of missing caller permissions.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-28 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 12:43 Frank Fesevur
2014-08-22 16:17 ` Yaakov Selkowitz
2014-11-06 17:51 ` Marco Atzeri
2014-08-25 7:47 ` Frank Fesevur
2014-08-28 8:22 ` Frank Fesevur
2014-08-28 10:06 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140828100611.GR20700@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).