We're going to need to know at least what version of Cyrus you are
running. Loading a core file with gdb and pasting a backtrace might be
helpful too.
Bron.
On Thu, Jun 18, 2015, at 12:40 AM, Jayesh Shinde wrote:
> Hi ,
>
>
I am facing problem with randomly mail delivery to local
ma
How long the system worked without problem before this ?
2.3.9 is very recent, what did you used before ?
What are the last chnage you did ?
A segfault is easyer to throbleshot, but need some work.
You need to find the source of the package, recompile it with debug
option enable, install it
and ru
søn, 01,.05.2005 kl. 10.18 +0200, skrev [EMAIL PROTECTED]:
> Hi everyone!
>
> I've installed Cyrus on my SuSE 9.2 professional and as I try to use
> cyradm with:
>
> cyradm localhost
>
> I enter my password and I receive:
>
> Segmentation fault
>
> I think it depends on SASL authentication or
On Mon, 29 Apr 2002, LiuJinhui wrote:
> Every I quit the cyradm, I got error message:
> Segmentation fault
>
> mailb:/var/spool/imap# cyradm -u root 202.118.66.103 9100
> Please enter your password:
> IMAP Password:
> 202.118.66.103> exit
> Segmentation fault
> ~~
[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Seva Adari wrote:
> Taking a clue from the above quote from 'info ld' (on a RedHat 6.2
> system), I have built SASL library with '-Wl,-Bsymbolic' flag for
> 'ld' and rebuilt imap
Seva Adari wrote:
> I guess it is SASL link references to imap and ldap and their own
> memory management seems to be the reason for the problem.
I have been fighting this on my own without finding a solution. If I
tell you I am on the OpenLDAP Project my fight will look rather pathetic,
but
Hi Julio,
I am glad that you are pursuing to resolve this issue, thanks.
`-Bsymbolic'
When creating a shared library, bind references to global symbols
to the definition within the shared library, if any. Normally, it
is possible for a program linked against a shared library to
Update:
I have downgraded my version of ldap to 1.2.11 and everything is working
fine. I guess it is SASL link references to imap and ldap and their own
memory management seems to be the reason for the problem.
How do I resolve such that SASL goes with either imapd or ldap memroy
functions but n
