[Kolab-devel] removing saslauthd.service at the end of the setup-kolab script

[Thomas Spuhler]

On Tuesday, May 14, 2013 02:43:16 PM Jeroen van Meeuwen wrote:
> On Tuesday, May 07, 2013 07:59:47 AM Thomas Spuhler wrote:
> > On Tuesday, May 07, 2013 04:44:38 AM Jeroen van Meeuwen (Kolab Systems)
> 
> wrote:
> > > On 2013-05-06 23:13, Thomas Spuhler wrote:
> > > > Why are we removing
> > > > saslauthd.service
> > > > 
> > > > at the end of setup-kolab?
> > > 
> > > We're not removing it, we're stopping it from starting on boot /
> > > runlevel changes.
> > 
> > Sorry for misstating. Why do you disable it. Is there a reason?
> 
> Yes, both saslauthd (from Cyrus SASL) and kolab-saslauthd would be
> listening (attempt to) on /var/run/saslauthd/mux.
> 
> In other words; they conflict and can not run at the same time.
> 
> Kind regards,
> 
> Jeroen van Meeuwen

Thanks for the clarification.This make sense.


-- 
Best regards
Thomas Spuhler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20130514/5c93761a/attachment.sig>