Dave- I've got the rsync daemon running as root, (setgroups() man page
said that if setgroups wasn't called as root it would give an error
message) and I've configured the ports correctly a la man page. I still
get the error with setgroups.
If it's a recently implemented security feature could I yank that section
out of the code and recompile it again? I haven't had a chance to really
delve into the code and fink around with it, honestly I've been trying to
avoid that:) The --daemon feature is the only
thing that's giving me trouble. I've gotten it to copy locally from
source
to source and at least start copying across a network(although it wasn't
very successful in terms of copying..it couldn't "find" a lot of
files/folders that were there) So unless nobody has gotten the --daemon
function working, I guess it's time to go code diving.
-Tito
--------------------------------------------
To heal will require real effort, and a change of heart, from all
of
us. To heal means that we will begin to look upon one another with
respect and tolerance instead of prejudice, distrust, and hatred.
---------------------------------------------
>
> Message: 1
> Date: Mon, 1 Jul 2002 10:36:09 -0500
> From: Dave Dykstra <dwd@bell-labs.com>
> To: rsync@lists.samba.org
> Subject: Re: rsync 2.5.5 and Mac OS X
>
> I compile rsync on Mac OSX (not sure of the osx version, but uname -a
> says it's darwin 5.5) but haven't tried running as a daemon. I
suggest
> that you try to debug it further. setgroups() is only called one place,
> in clientserver.c, with parameters setgroups(0, NULL), and only if
> the define HAVE_SETGROUPS is set. This call was a relatively recent
> security fix addition to rsync. The OSX setgroups man page says that the
> EINVAL error is only supposed to occur if the first parameter is greater
> than NGROUPS_MAX. Apparently it is also reporting that error if the first
> parameter is zero.
>
> - Dave Dykstra
>
>
