Kolab on Debian Etch

[Saim Kim]

Hello Alex,

that quote was for the Kolab 2.1 release version which I tried as an 
alternative. For the Kolab 2.2 rc2 you are right.

Can it be that it is a problem with the DNS lookup? Since I don't use an 
DNS->IP resolving (can't connect to the Kolab server by the fqdn). But 
the webadmin and the Toltec Connector run fine if I directly enter the 
IP of my Kolab server.

Cheerio,
Saim




Alex Chejlyk schrieb:
> Saim Kim wrote:
>
> Quote:
> "I used the "# sh obmtool kolab 2>&1 | tee kolab-build.log" command as 
> described in the readme
> of the sources.
>>>> Greets,
>>>> Saim
>
> Saim,
>
> The proper build switched for the kolab-install scripts would be -H 
> for Horde and -F for Freebusy.
>
> If you build from the debian binaries:
>
> ./install-kolab.sh -H -F 2>&1 | tee kolab-install.log
>
> Cheers,
>
> Alex C.
>
>
>


-- 
--------------------------------------------------------------------------
Dipl.-Ing. Saim Kim
Lehrstuhl fuer Medizinische Informationstechnik
Helmholtz-Institut fuer Biomedizinische Technik
RWTH Aachen
Pauwelsstr. 20, D-52074 Aachen
---
Web:   http://www.medit.hia.rwth-aachen.de/
Tel:   +49-(0)241-80 23218
Fax:   +49-(0)241-80 82442
email: s.kim at hia.rwth-aachen.de
--------------------------------------------------------------------------