[Kolab-devel] removing saslauthd.service at the end of the setup-kolab script
Jeroen van Meeuwen
vanmeeuwen at kolabsys.com
Tue May 14 23:43:16 CEST 2013
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
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
More information about the devel
mailing list