Description of problem:
All the mistakes I made in my first eval of the install came about answering the
questions in the install script, The username pw entry screens tended to confuse
rather than be self explanatory, not sure of the solution
Pehaps a 1 or 2 line entry for each step
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Could you be more specific about individual screens/prompts and their wording?
I finally had time to go back & do some uninstall & re installs on the test
system to define my problems better
My biggest problem it turns out was poor definition of dns, if an error occurs
in the installer script the admin scripts are not created & admin config files
not written so cant go back & manually correct them
Suggest better messages re cause of script failure & perhaps a pause on error to
allow correction of problem & then continue set up script
As for confusion, where the (name) is in the prompt I did not at first realise
it was the last entry I made, my fault, must have been a bit slow that day
Where the system user to run DS is suggested (nobody) & a non default name is
entered, then a prompt to create a valid system user external to the script or
auto creation of the non default user could be put into the script
One other observation, a mismatch in the name of the FC5 rpm to the software
actually installed made ininstall a little more complicated than normal
Anyway thanks & I think problems more me on that day than anything
We should make sure the docs specify that DNS and reverse DNS must be working
correctly, especially if using TLS/SSL or Kerberos.
The RPM should create the user - this is the usual way service RPMs work.
User email@example.com's account has been closed
Reassigning to me.
There was alreayd a DNS/NIS section for Solaris; I used added this text to RHEL
and HPUX, then I added the above note about making sure DNS and reverse DNS is
working for TLS/SSL/Kerberos.
It is very important that DNS and reverse DNS be working correctly on the host
machine, especially if you are using TLS/SSL or Kerberos with Directory Server.
Configure the DNS resolver and the NIS domain name by the modifying the
/etc/resolv.conf, /etc/nsswitch.conf, and /etc/netconfig files, and set the DNS
resolver for name resolution.
Edit the /etc/defaultdomain file to include the NIS domain name. This ensures
that the fully-qualified host and domain names used for the Directory Server
resolve to a valid IP address and that that IP address resolves back to the
Reboot the Red Hat Enterprise Linux machine to apply these changes.
Changing modifieds to ON_QA.