I am trying to set up a MacOS X rsync server and am not having much success at the moment. I'm able to see the "share" alright, but here is what I get when I actually try to copy anything to the server: #rsync -vz /Users/myhome localhost::backup @ERROR: setgroups failed rsync: connection unexpectedly closed (37 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) I get the same result on any linux server I try this from as well. My simple trial rsyncd.conf is: [backup] path = /Volumes/Backup comment = Backup Directory for OS X read only = false Any thoughts as to why this is happening?
On Wed, Feb 19, 2003 at 12:28:58AM -0500, lists wrote:> I am trying to set up a MacOS X rsync server and am not having much > success at the moment. I'm able to see the "share" alright, but here > is what I get when I actually try to copy anything to the server: > > #rsync -vz /Users/myhome localhost::backup > @ERROR: setgroups failed > rsync: connection unexpectedly closed (37 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(150) > > I get the same result on any linux server I try this from as well. > > My simple trial rsyncd.conf is: > > [backup] > path = /Volumes/Backup > comment = Backup Directory for OS X > read only = false > > Any thoughts as to why this is happening?OSX has a problem with zeroing supplemental groups? Start by looking in the daemon log (probably going to syslogd) and see what the errno is. Frankly it should be almost impossible to have this error if autoconf is getting it right. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt
Please don't mail to me seperately. It makes identifying whether this was also sent to the list (where it belongs) difficult. CCing me is OK as that gets filtered. (oops i forgot to CC the list and just broke this rule myself) On Wed, Feb 19, 2003 at 06:42:47PM -0500, George D. Plymale wrote:> I was able to build the rsync 2.5.5 package with your below suggested > option and it is now working as a daemon apparently without issue.If you are distributing that please include an errata that the daemon should be launched by root with no suplimentary groups. The supplimentary groups would be inherited by all modules chrooted or not and that would effectively bypass the gid option.> > Please advise as to the next step we can take. If someone who has the > time or familiarity with darwin/xnu source to pinpoint the problem that > would be great as we could forward this information on to Bill > Bumgarner for Apple resolution. > > Thanks, > > -George PlymaleIt shouldn't be too difficult to pin down the problem. It might be as simple as copyin, or whatever the darwin equivalent of copy-from-user, trying to act before size has been checked for 0. It might be possible to test for that without looking at source by simply passing a valid pointer to setgroups ala setgroups(0, "\0") (i suggest it only as a test and do not advocate doing that ugliness in rsync) The real problem will be getting a fix incorporated into shipped product.