On 29/04/2013 23:08, Daniel Shahaf wrote:
>
> Instead of hoping, just uncomment it and set it to "false".
>
Tried that... no change, unfortunately. Thanks for the thought, though.
Steve.
On 30/04/2013 09:52, Philip Martin wrote:
If built with SASL support then svnserve always initialises the SASL
subsystem. This must be done if SASL is to be available and at this
stage the server doesn't know which repositories will be accessed.
It appears to be the SASL libraries that are pro
raichea writes:
> "Cyrus SASL authentication is available."
>
> So I think you're right. However, as the use-sasl entry in the conf
> file is commented out (along with all the other sasl stuff) I would
> hope it's not trying to use it
If built with SASL support then svnserve always initialise
raichea wrote on Mon, Apr 29, 2013 at 23:01:51 +0100:
> On 29/04/2013 21:55, Daniel Shahaf wrote:
>>
>> The fact it's commented out rather than not present implies svnserve was
>> built with SASL support; 'svnserve --version' will confirm that.
>>
>> Just a possibly-relevant fact...
>>
>> Daniel
>>
On 29/04/2013 21:55, Daniel Shahaf wrote:
The fact it's commented out rather than not present implies svnserve was
built with SASL support; 'svnserve --version' will confirm that.
Just a possibly-relevant fact...
Daniel
Hmm, thanks... well, the output from that command includes:
"Cyrus SASL
raichea wrote on Mon, Apr 29, 2013 at 14:28:30 +0100:
> I repeatedly get this message in my server log.
>
> Googling has shown that I'm not alone, although not everyone reports the
> message coming from svn. Other than that, it has shed little light on
> what the problem might be apart from it
I repeatedly get this message in my server log.
Googling has shown that I'm not alone, although not everyone reports the
message coming from svn. Other than that, it has shed little light on
what the problem might be apart from it being somehow related to SASL.
My SVN server is not using SASL
