Strategies to implement kolab

[Luca Fornasari]

The exercise here is to have Kolab installed from sources (including 
apache etc) and samba plus a second instance of apache and other stuff 
from the Debian repository. Obviously samba will use the same LDAP 
server so users will have one profile and one password only ...

Running kolab and samba on the same machine is very easy if you do samba 
authentication against tdb or smbpasswd.
When you want to authenticate against LDAP it starts to be a little 
problemtic ... just a little!

Regards

Luca Fornasari
FURNA.COM



-------- Original Message --------
Subject: Re: Strategies to implement kolab
From: Paul Franklin <pdf at yugm.org>
To: Kolab Users <kolab-users at kolab.org>
Date: Wed Dec 12 2007 02:17:43 GMT+0800 (HKT)
> On my machine at home, I have both kolab and samba running on the same 
> server without having made any edit to /kolab/etc/kolab/templates.  It 
> seems to have been operating just fine for about 7 months.  Am I heading 
> for a cliff?
> --Paul
>
>
> Gunnar Wrobel wrote:
>   
>> Hi Luca,
>>
>> Luca Fornasari <luca at furna.com> writes:
>>
>>   
>> 2) Since I love Debian and this server also must run samba I'd like to
>>     
>>> have kolab running from /kolab and at the same time the rest of the 
>>> distribution running as usual. Sounds doable binding the correct daemons 
>>> to the right IP addresses. I guess the right way to do this is to edit 
>>> templates files in /kolab/etc/kolab/templates to bind the daemons to the 
>>> correct ip addresses. Am I correct?
>>>     
>>>       
>> Yes. As long as you don't use a single port on the same IP twice ;)
>> you should be fine and both environments won't disturb each other.
>>
>>   
>>