Recommended update for package yast2-openteam-server

Knowledgebase

(Last modified: 12JAN2004)

solutions Recommended update for package yast2-openteam-server SuSE Linux Maintenance Web (9390d772f5d58f093627985da6a8d0e5)

Applies to

Product(s): SuSE Linux Openexchange Server 4

Package: yast2-openteam-server
Release: 20040112
Obsoletes: none

Indications

This patch should be installed.

Contraindications

None.

Problem description

The YaST2 module which ships with SLOX 4.1 has a bug that disallows to set up a dns/dhcp server on a not class bounded (A,B or C) network.
Using this updated module, the problem can be fixed after a finished SLOX 4.1 installation.

Solution

Please install the updates provided at the location noted below.

Installation notes

Install the provided update package: rpm -Uvh yast2-openteam-server.rpm
Start the module using the following syntax: yast2 openteam createDNSLDAP [iface] In the above command, replace [iface] with the correct network interface (default: eth0). Example: yast2 openteam createDNSLDAP eth0 After the module has been finished, there will be a new file /var/lib/ldap/dnszone.ldif and the old one will be deleted.
To delete the old LDAP DNS tree, issue the command: ldapdelete -r -x -D"uid=cyrus,BASEDN" -w PASSWORD "o=DNS,BASEDN" For PASSWORD please substitute your cyrus admin password and BASEDN with the one used on your system. If you are unsure about the correct BaseDN, please take the one from /etc/openldap/ldap.conf.
To add the new LDAP tree, please issue this command: ldapadd -x -D"uid=cyrus,BASEDN" -w PASSWORD -f /var/lib/ldap/dnszone.ldif Please be sure to enter the correct PASSWORD and BASEDN.

links to download packages

SUSE Linux Openexchange Server 4 (i386)

Download Source Packages

Download the source code of the patches for maintained products.

Disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.

Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.