Greetings!
I just did a fresh install of DU 4.0D. I activated enhanced security and
applied jumbo patch #3. Next I configured the default user template for
the password controls, login restrictions, etc that I want. I then created
a user. Everything seemed normal enough. However, I then encountered the
following problems:
1. I attempted to log in as my new user in a command line session on the
console. This acted oddly because the dtlogin screen kept coming back
every few seconds. Note: My new user's password expired at once so I was
trying to set a new password at the time. Yet even after I managed (with
difficulty -- I had to constantly go back to the "command line session")
to get my new user logged in, the dtlogin screen continued to interrupt my
session.
2. I managed to log my new user out. I then tried to log in as root using
dtlogin. When I do this the screen clears and I see "Starting CDE
Environment" and then the screen immediately returns to the dtlogin
screen. Just before the screen clears I can see some messages being
written into the console log window. However I can't read them. They say
something like "fatal error... can't load {somesuch}." I *can* log in as
root in a command line session and that seems to be well behaved.
3. When I try to modify my new user's password with passwd, I'm told the
user does not exist. However, the user does exist (I can see the entry in
/etc/passwd!). For fun I ran mkpasswd on the password file, but that did
not fix this issue.
My questions:
a) Is the console log written to a file some place? I'd love to read those
messages once I get logged in using the command line.
b) Why does my root graphical login no longer work?
c) Why did dtlogin keep interfering with the command line login of my new
user?
d) Why does passwd believe my new user does not exist?
Received on Wed Jan 20 1999 - 13:01:42 NZDT