Rich Wales wrote, at 11/14/2007 06:13 PM:
> It looks like my problem with replication not working in one direction
> was a SASL thing. One of my servers was advertising GSSAPI as an
> authentication mechanism, but it didn't really work (I don't have
> Kerberos installed on my systems). Apparently
> I'm mildly concerned that a future software upgrade might cause these
> libraries to reappear. Is there a more reliable way to disable SASL
> authentication mechanisms, other than removing files from the library
> directory?
Set sasl_mech_list to the list of mechanism you wish to support.
For
Hi Rich,
That truly depends on how your Unixlike (Linux) handles the package. If
you're using a rpm, you may want to look into using a SRPM the next time
and tweek the .spec file so it does not try and pull in ntlm and otp and
gssapi.
That's one thing I dislike about most package management s
It looks like my problem with replication not working in one direction
was a SASL thing. One of my servers was advertising GSSAPI as an
authentication mechanism, but it didn't really work (I don't have
Kerberos installed on my systems). Apparently, sync_client on the
other box was deciding to use
My earlier problem with "synctest" turned out to be caused by my not
specifying an authentication name ("-a" argument on the command line).
Since I didn't have an "-a" argument, "synctest" apparently decided
to use my account name (from the USER environment variable?) as the
authentication name --
>> On Nov 13, 2007 8:08 AM, Rich Wales <[EMAIL PROTECTED]> wrote:
>>> OK, so I decided to try what I described earlier (replication in both
>>> directions, with different users using different master servers) . . .
>>> .
>>>
>>> But now I'm running into an authentication problem. One of my servers
> On Nov 13, 2007 8:08 AM, Rich Wales <[EMAIL PROTECTED]> wrote:
>> OK, so I decided to try what I described earlier (replication in both
>> directions, with different users using different master servers) . . . .
>>
>> But now I'm running into an authentication problem. One of my servers
>> (my o
On Nov 13, 2007 8:08 AM, Rich Wales <[EMAIL PROTECTED]> wrote:
> OK, so I decided to try what I described earlier (replication in both
> directions, with different users using different master servers) . . . .
>
> But now I'm running into an authentication problem. One of my servers
> (my original
OK, so I decided to try what I described earlier (replication in both
directions, with different users using different master servers) . . . .
But now I'm running into an authentication problem. One of my servers
(my original replica) simply refuses to authenticate to the other one
(my original m
