can kolab conflict with egw ?

Mon Dec 18 11:35:15 CET 2006

Op maandag 18 december 2006 11:23, schreef u:
> Now I can understand.  I installed kolab when my egw was running under
> xampp. but I have problem to
> understad about *template* u talking about. where is that template
> directory of kolab actually ?

It is in /kolab/etc/kolab/templates
This contains all the configuration files for kolab. You can edit the ones 
in /kolab/etc, but they get overwritten with the templates at every reboot. 
So any configuration should occur in the templates directory.

>
> one more thing, I have also seen the .rpm packages of kolab for
> open-suse 10.1.
> does these all base on openpkg architecture or simply install the .rpm
> pacakes in suse ?

Eh... I dont know, the openpkg architecture should work fine for open-suse as 
well, but I dont have any personal experience with that.

Anyone else?

Greetings & salutations,

Ger Apeldoorn.

> thanking you
>
> Ger Apeldoorn wrote:
> > You need to stop your apache during the installation of kolab. Only after
> > installation you can configure kolab to NOT listen to port 80.
> >
> > (Remember, you need to do that in the templates directory!!)
> >
> > Ger.
> >
> > Op maandag 18 december 2006 10:45, schreef JOYDEEP:
> >> But it is not working in this way. I have set "Listen 80" in the
> >> apache.conf of xampp and
> >> "Listen 443" in the apache.conf of kolab. but kolab still reports
> >>
> >> KOLAB BOOTSTRAP
> >> Check for running webserver on port 80
> >> Error: Found webserver running on Port 80
> >> Check your installation!
> >> You must stop the service webserver before running Kolab
> >>
> >> :-(
> >>>
> >>> Ger Apeldoorn wrote:
> >>> Hi,
> >>>
> >>> Yes, that is possible.. It will not conflict in that way.
> >>> With IMAP, you can specify an SSL port for one and no SSL for the other
> >>> too. I dont know about LDAP though.
> >>>
> >>> Ger.
> >>>
> >>> Op maandag 18 december 2006 10:33, schreef u:
> >>>> Hi Ger,
> >>>>
> >>>> is it possible to run two apache servers on two different port ?
> >>>> you have advised to run two apache with two different address but what
> >>>> about
> >>>> running the apache of egw at port 80 and apache of kolab at port 443
> >>>> of the same ip ?
> >>>>
> >>>> please let me know.
> >>>>
> >>>> Ger Apeldoorn wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I can tell you how to add an interface; but it varies from distro to
> >>>>> distro.
> >>>>>
> >>>>> I will assume your nic's ipaddress is 192.168.0.1 and the new one
> >>>>> will be 192.168.0.2
> >>>>>
> >>>>> On RedHat:
> >>>>> 1st, configure a static ipaddress for your first interface. (You
> >>>>> probably already did)
> >>>>> In this directory: /etc/sysconfig/network-scripts/
> >>>>> cp ifcfg-eth0 ifcfg-eth0:0
> >>>>> then edit ifcfg-eth0:0
> >>>>> --------------------%<------------------------
> >>>>> DEVICE=eth0:0
> >>>>> BOOTPROTO=static
> >>>>> HWADDR=00:16:35:04:3B:AB
> >>>>> ONBOOT=yes
> >>>>> TYPE=Ethernet
> >>>>> IPADDR=192.168.0.2 (another address)
> >>>>> NETMASK=255.255.255.0
> >>>>> NETWORK=192.168.0.0
> >>>>> GATEWAY=192.168.0.1
> >>>>> --------------------%<------------------------
> >>>>>
> >>>>> APACHE listening on the old interface:
> >>>>> Change the Listen directive
> >>>>> --------------------%<------------------------
> >>>>> Listen 192.168.0.1:80
> >>>>> Listen 192.168.0.1:443
> >>>>> --------------------%<------------------------
> >>>>>
> >>>>> APACHE listening on the new interface:
> >>>>> Change the Listen directive
> >>>>> --------------------%<------------------------
> >>>>> Listen 192.168.0.2:80
> >>>>> Listen 192.168.0.2:443
> >>>>> --------------------%<------------------------
> >>>>>
> >>>>> This is what I have, for the other services, you've got to hit the
> >>>>> documentation yourself.. :)
> >>>>>
> >>>>> Good luck
> >>>>> Ger Apeldoorn.
> >>>>>
> >>>>> Op maandag 18 december 2006 05:36, schreef u:
> >>>>>> Hi Ger Apeldoorn,
> >>>>>>
> >>>>>> finally I have decided to go for the solution no. #3 means having a
> >>>>>> virtual network interface to run both egw and kolab. could you
> >>>>>> kindly explain how to do that ?
> >>>>>>
> >>>>>> thanks for your time.
> >>>>>>
> >>>>>> Ger Apeldoorn wrote:
> >>>>>>> No problem, i'll try to explain properly.
> >>>>>>>
> >>>>>>> Normally, you cannot have two identical services on the same server
> >>>>>>> because a process listens to a specific port.
> >>>>>>> For instance, http servers listen to port 80 on all ip-adresses.
> >>>>>>> If one is already listening you can try to start the second but it
> >>>>>>> will complain that the address is already in use because it cannot
> >>>>>>> listen to the port it desires.
> >>>>>>>
> >>>>>>> You can do several things to circumvent this problem:
> >>>>>>> 1) stop (and disable) the other (egw) services before you start the
> >>>>>>> kolab services
> >>>>>>> 2) give the egw services (or the kolab services) other ports
> >>>>>>> 3) add a virtual network interface with its own ipaddress to your
> >>>>>>> server and configure ALL egw and kolab services to bind to their
> >>>>>>> own ip-address only. 4) use Xen or VMWare to install a virtual
> >>>>>>> server and install kolab there 5) buy an extra server
> >>>>>>>
> >>>>>>> 1) is the easiest part but egw will not be available (for testing?)
> >>>>>>> 2) will probably break things and if not, the clients must use
> >>>>>>> another portnumber (not the default one which are mostly
> >>>>>>> preconfigured in mailclients etc) to connect to the services like
> >>>>>>> IMAP and LDAP 3) is probably the best solution if you want to run
> >>>>>>> egw and kolab on the same server but will require some knowledge
> >>>>>>> and faq-reading 4) I dont have any experience with Xen, but VMWare
> >>>>>>> is pretty easy and free (as in beer).
> >>>>>>> 5) this will cost you money... :)
> >>>>>>>
> >>>>>>> If you select an option, perhaps i can help you further.
> >>>>>>>
> >>>>>>> Good luck,
> >>>>>>>
> >>>>>>> Ger Apeldoorn
> >>>>>>>
> >>>>>>> Op vrijdag 15 december 2006 13:23, schreef JOYDEEP:
> >>>>>>>> I am afraid to say the concept is not very clear to me.
> >>>>>>>> may be due to my lack of knowledge.
> >>>>>>>>
> >>>>>>>> but what if we change the apache, imap and ldap of kolab to work
> >>>>>>>> with diferent port
> >>>>>>>> than that of egw ?
> >>>>>>>>
> >>>>>>>> I am also like to understand the solution u have provided ?
> >>>>>>>> could you kindly provide some more info ?
> >>>>>>>>
> >>>>>>>> thaks for your kind response.
> >>>>>>>>
> >>>>>>>> Ger Apeldoorn wrote:
> >>>>>>>>> Yes, it probably will.. They use the same ports. You can add
> >>>>>>>>> another ipaddress to the server and make each service listen to
> >>>>>>>>> only that address.
> >>>>>>>>>
> >>>>>>>>> Ger Apeldoorn.
> >>>>>>>>>
> >>>>>>>>> Op vrijdag 15 december 2006 11:58, schreef JOYDEEP:
> >>>>>>>>>> Dear list,
> >>>>>>>>>>
> >>>>>>>>>> Like to ask one thing. does imap and ldap of kolab will conflict
> >>>>>>>>>> with the existing IMAP and LDAP required for my egw ?
> >>>>>>>>>>
> >>>>>>>>>> thanks
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> Kolab-users mailing list
> >>>>>>>>>> Kolab-users at kolab.org
> >>>>>>>>>> https://kolab.org/mailman/listinfo/kolab-users
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> Kolab-users mailing list
> >>>>>>>> Kolab-users at kolab.org
> >>>>>>>> https://kolab.org/mailman/listinfo/kolab-users
> >>
> >> _______________________________________________
> >> Kolab-users mailing list
> >> Kolab-users at kolab.org
> >> https://kolab.org/mailman/listinfo/kolab-users

-- 
ARGOSS: your partner for atmospheric, marine & coastal information
P O Box 61
8325ZH Vollenhove The Netherlands
tel +31-527-242299 fax +31-527-242016
Web http://www.argoss.nl

Confidentiality Notice & Disclaimer
The contents of this e-mail and any attachments are intended only for the
use of the e-mail addressee(s) shown. If you are not that person, or one of
those persons, you are not allowed to take any action based upon it or to
copy it, forward, distribute or disclose the contents of it and you should
please delete it from your system.

ARGOSS Holding BV and its subsidiaries do not accept any liability for any
errors or omissions in the context of this e-mail or its attachments which
arise as a result of Internet transmission, nor accept liability for
statements which are those of the author and not clearly made on behalf of
ARGOSS.