Re: Solaris (11) support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jean-Crishtophe,

we use Cyrus on Solaris, but at the moment, haven’t used Murder -
so can’t offer advice etc on that one directly.

We’ve got a couple of big projects under way at the moment
for some customers - once we’ve got those sorted, I can try to
get a test setup going and see what happens - but it would be
in a couple of weeks time at the earliest…

marty


-----
Marty Lee                         e: marty@xxxxxxxxxxxxxxxxxx
Technical Director                v: +44 131 564 1980
Maui Systems Ltd                  w: http://www.maui-systems.co.uk  
Scotland, UK                      

> On 18 Jun 2018, at 11:03, Jean-Christophe Delaye <Jean-Christophe.Delaye@xxxxxxxxxx> wrote:
> 
> On 06/18/2018 05:25 AM, ellie timoney wrote:
>> Hi Jean-Christophe,
> 
> Thanks Ellie for your inputs.
>> 
>> On Fri, Jun 15, 2018, at 5:49 PM, Jean-Christophe Delaye wrote:
>>> So this is why the first part of my
>>> question was to known if there are many running murder systems running
>>> on Solaris (11) and why I can't find specifics notes about
>>> compiling/installing Cyrus imapd on this operating system.
>> 
>> The main contributors to Cyrus development are not running Solaris, either personally or organisationally, so Solaris support doesn't get a lot of direct attention.
>> 
>> There are a few people out there running Cyrus on Solaris (not sure if they're using murder or not).  They usually pop up on the list with Solaris-compatibility issues/patches not long after new releases where we've accidentally broken something on Solaris, which we greatly appreciate! :)
> 
> Yes, I tried the running unit tests (Version 2.1-3) on my setup and
> found the following issue on the backend:
> 
> Suite: backend
>  Test: badhost ...passed
>  Test: badservice ...passed
>  Test: sasl_plain ...Server failed to find requested SASL mechanism
> "PLAIN" FAILED
>    1. ./cunit/backend.testc:198  - CU_ASSERT_PTR_NOT_NULL_FATAL(be)
>  Test: sasl_digestmd5 ...passed
>  Test: multiline_caps ...Server failed to find requested SASL mechanism
> "PLAIN" FAILED
>    1. ./cunit/backend.testc:314  - CU_ASSERT_PTR_NOT_NULL_FATAL(be)
>  Test: oneline_caps ...Server failed to find requested SASL mechanism
> "PLAIN" FAILED
>    1. ./cunit/backend.testc:314  - CU_ASSERT_PTR_NOT_NULL_FATAL(be)
>  Test: starttls ...Server failed to find requested SASL mechanism
> "PLAIN" FAILED
>    1. ./cunit/backend.testc:408  - CU_ASSERT_PTR_NOT_NULL_FATAL(be)
> 
> But,it's not easy for me to go further; I'll continue investigating....
> 
> 
> Run Summary:    Type  Total    Ran Passed Failed Inactive
>              suites     39     39    n/a      0        0
>               tests    432    432    427      5        0
>             asserts 829800 829800 829795      5      n/a
> 
> 
> Cheers
> 
>> 
>> I have no access to Solaris, and so additional insight to offer.  But I'd be very happy to accept/merge patches to code/documentation for you if you get things working properly.
>> 
>> Cheers,
>> 
>> ellie
>> ----
>> Cyrus Home Page: http://www.cyrusimap.org/
>> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>> To Unsubscribe:
>> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>> 
> 
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus




[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux