Installation guide

Workaround: Restart Account Manager and then delete the template.
• After deleting a template, the NIS maps are not remade.
Workaround: Manually remake the NIS maps or perform an Account
Manager function (for example, Account Modification) that will trigger
the maps to be remade. To manually remake the maps do the following:
# cd /var/yp
# make all
4.2.2 BIND Configuration
The following problems apply to configuring BIND servers with the BIND
configuration graphical user interface.
• Once entered, a zone cannot be deleted by clicking on the delete button in
the Zones window.
Workaround: Edit the /etc/namedb/named.boot file to remove the
zone entry that needs to be deleted.
• At least one Forwarder must be entered in the Forwarder window if any
Zones are to be added.
Workaround: If the Forwarder is not needed, you can edit the
/etc/namedb/named.boot file to remove the Forwarder entry after
you Commit to the setup in the BIND configuration interface.
• If your host is already configured as BIND server, and the BIND
configuration interface is used to add, delete, or append forwarders, all of
the existing Zones in /etc/namedb/named.boot file will be deleted
if the Zones button is not clicked first.
Workaround: Whenever you modify your BIND setup using the BIND
configuration interface, click on the Zones button before you Commit to
any changes.
• The Server Addr field of secondary domain in the Modify Zone window
cannot be modified using the BIND configuration interface.
Workaround: The address can be modified by editing the secondary
domain entry in the /etc/namedb/named.boot file.
4.2.3 The dxshutdown Application Does Not Prohibit Logins
The dxshutdown application does not create the /etc/nologin file as
described in the documentation. This means that users will be able to log in
to a machine that is being shut down up until the actual time of the shut
down.
Base System Software Notes 4–13