Sorry for the late summary, but my Alpha system crashed for a power
failure.
After the boot, all works fine.
My original question was:
> Hello everybody,
>
> on an Alpha system, all users can login just fine, using CDE.
> Only one user get the following message:
>
> Action Required
>
> The DT messaging system could not be started.
> To correct the problem:
> 1. Choose [OK] to return to the login screen
> 2. Select Failsafe Session from the login screen's option
> menu and log in.
> 3. Check to see that your hostname exists correctly in /etc/hosts if your
> network has already been configured.
> 4. If your network has not yet been configured; make sure that /etc/hosts
> has the following entry in it:
> 127.0.0.1 localhost
>
> The same user can login on other systems, and the user's home dirs are shared
> across the systems using DMS + NFS.
>
> I've checked /etc/hosts and it seems O.K.:
>
> 127.0.0.1 localhost
> 140.105.7.148 ag3ts0.ts.infn.it ag3ts0
> 140.105.7.152 ag3ts2.ts.infn.it ag3ts2
> 140.105.6.153 axts03.ts.infn.it axts03 # BIND server
> 140.105.48.16 uts.univ.trieste.it uts # BIND server
>
> (The Alpha is 140.105.7.152)
>
> I've checked the permissions on this file and it seems O.K. too:
>
> -rw-r--r-- 1 root system 2101 Aug 14 11:31 /etc/hosts
>
> Any suggestions?
> Thanks in advance!
>
> Lucio
Many thanks to:
Thomas M. Payerle <payerle_at_physics.umd.edu
Oyanarte Portilho <portilho_at_fis.unb.br>
John F. Marten <root_at_tigger.oslc.org>
Thomas says:
> I haven't used CDE too much on alphas, but have some experience with it on AIX
> boxes. Check the users login scripts .login, .cshrc/.profile, and .dtprofile
>
> In particular, you may wish to look at the
> DTSOURCEPROFILE setting in .dtprofile; if set to true, set it to false and
> see if he can login in. CDE can get some wierd behavior if DTSOURCEPROFILE
> is set to true and login scripts contain terminal orientated commands.
> Following is extracted from .dtprofile from AIX system, should probably apply
> reasonably well to alpha
>
> ### Personal environment variables can be set in the script file
> ### "$HOME/.dtprofile". The files /etc/profile and $HOME/.profile are
> ### not read by DT as they may contain terminal I/O based commands
> ### inappropriate for a graphical interface. Users should set up
> ### ".dtprofile" with personal environment variables for their DT
> ### session.
> ###
> ### DT will accept either sh or ksh syntax for the commands in this
> ### file. The commands should only be those that set environment
> ### variables, not any that perform terminal I/O, ex. "tset" or "stty".
> ###
> ### With minor editing, it is possible to adapt $HOME/.profile (.login)
> ### for use both with and without CDE DT. Group the statements not
> ### allowed for DT into one section and enclose them with an "if"
> ### statement that checks for the setting of the "DT" environment
> ### variable. Then set the "DT" environment variable at the bottom of
> ### this script (.dtprofile) and log in again. From then on changes
> ### need only be made to $HOME/.profile (.login).
> ###
> ###
> ### example for sh/ksh
> ###
> ### #
> ### # commands and environment variables used when logging in without DT
> ### #
> ### if [ ! "$DT" ]; then
> ### stty ...
> ### tset ...
> ### DISPLAY=mydisplay:0
> ### MAIL=/usr/mail/$USER
> ### EDITOR=/bin/vi
> ### ...
> ### fi
> ###
> ### #
> ### # environment variables common to both DT and non-DT
> ### #
> ### PATH=$HOME/bin:$PATH
> ### ...
> ###
> ### Errors in .dtprofile or .profile (.login) may prevent a successful
> ### login. If so, log in via the Fail-safe session and correct the error.
Oyanarte says:
> I suggest you to check permissions/ownership of the files
>
> /etc/svc.conf
> /etc/resolv.conf
>
> They shall be 755 bin bin.
John says:
> try one of these:
> look at .xsession-errors or at /var/X11/xdm/xsession-errors
> look at /.dt/sessions/errorlog and /.dt/sessions/startlog
> look at .profile and /.dtprofile make sure no code is executed
> from /.dtprofile
> try commenting out #DTSOURCEPROFILE=true
>
> and this may be reaching but check in /etc and delete .AM_is_running
> if there is one.
>
> if none of that works write me back i have one more trick.
Received on Tue Oct 06 1998 - 07:31:56 NZDT