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

[Thomas Spuhler]

On Monday, May 06, 2013 11:45:25 PM Paul Klos wrote:
> Thomas Spuhler schreef op 07.05.2013 00:13:
> > Why are we removing
> > saslauthd.service
> > 
> > at the end of setup-kolab?
> 
> Kolab uses its own saslauth daemon, which on Debian is called
> kolab-saslauthd.
> 
> > MySQL roundcube password [nlZ6BnGAykML8u3]:
> > Confirm MySQL roundcube password:
> > rm '/etc/systemd/system/multi-user.target.wants/saslauthd.service'
> 
> Not a systemd user myself, I don't know about this. On Debian the
> default saslauthd gets stopped and disabled, not removed. Would that
> work here as well?
This is what's being done

systemctl disable saslauthd 

will respond with  rm '/etc/systemd/system/multi-user.target.wants/saslauthd.service'
and it will not start the next boot

when you do 
systemctl enableable saslauthd 
it will make it start the next boot.

> 
> Cheers,
> 
> Paul
> 
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://www.intevation.de/mailman/listinfo/kolab-devel

-- 
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/1b62a17e/attachment.sig>