It is currently Thu, 30 Oct 2014 06:22:16 GMT



 
Author Message
 CDE not working anymore
Jamie,

A few Pointers....

kind regards Aamir

http://www.**-**.com/

Application Does Not Start from Home Session in CDE

--------------------------------------------------------------------------------

Problem
An application does not start from the home session in the Common
Desktop Environment.

Although Session Manager reads the $HOME/.dt/sessions/home or
$HOME/.dt/sessions/current to set up the session when you log in, it
does not start up some applications. This includes some shell scripts,
applications that are not programmed for CDE, and some older
applications that do not recognize CDE.

When you try to set one of these applications to start up from your
home or current application, it does not come up. You also do not see
any errors logged in the $HOME/.dt/errorlog. In addition, when you
change directories to $HOME/.dt/sessions/home and search using the
grep command for the application that you are trying to start, it does
not appear.

This is not a problem with CDE. The application does not use the
protocols that the Session Manager uses.

NOTE: Applications that do not start up from the home session are
non-ICCCM compliant. They do not write their command line to the
WM_COMMAND property (in xprop). ICCCM is CDE compatible. ICCCM
expanded is Inter-Client Communication Conventions Manual. For more
information, see Interclient Communication and Interclient
Communication Window Managers and Shells

--------------------------------------------------------------------------------

Solution
If you need an application to start when you log in, you can create a
file in $HOME/.dt/sessions called sessionetc. In this file, type the
command you would like to execute. Type this command just as you would
when executing the command from a dtterm or xterm.

Example:

If you want to start Netscape when you log in and it does not start
through your home session, you can create the sessionetc file and put
in the following line:

/usr/bin/netscape

CDE Does Not Work with HACMP

--------------------------------------------------------------------------------

Problem
CDE is not working with HACMP.

--------------------------------------------------------------------------------

Solution
The reason that CDE is not functioning is that in HACMP rotating mode,
the IP addresses of the HACMP cluster are "rotated." This causes
problems with CDE because CDE is very network dependent and needs to
resolve the hostname and IP address of the system.

Some possible solutions follow:

You cannot use HACMP in rotating mode. You must be in concurrent or on
the master in a cascading mode system.
Also ensure that dtlogin is being started after HACMP and that HACMP
has not been stopped since dtlogin was started.
Assigning a network interface that is NOT part of the HACMP cluster as
the primary interface to the machine will enable CDE to function
properly.
If you need to run a GUI interface, and you are unable to change from
rotating mode and unable to assign a interface that is not part of the
HACMP cluster, you can run XDM instead of CDE.

CDE Hangs at Blue Screen - Name Resolution/Network OK

--------------------------------------------------------------------------------

Problem
CDE hangs at blue screen even though all names are resolved, the
network is stable, the filesystems are not full, and enough paging
space exists.

--------------------------------------------------------------------------------

Solution
The MANPATH in /etc/environment has been modified. As root, using your
preferred editor, edit this out.

CDE Hangs on Blue Screen or dtmessaging Does Not Start

--------------------------------------------------------------------------------

Problem
The Common Desktop Environment (CDE) hangs on the blue screen or you
cannot start dtmessaging.

--------------------------------------------------------------------------------

Solutions
When CDE is initialized, it must be able to resolve its hostname,
ensure that it has access to all hosts, and resolve those hosts
defined for the system.

Who is affected? If all users are not affected, first check the
following list.

Filespace in /home and /var
Permissions on /dev/null (666)
Permissions on /dev/lft0 (666)
Permissions on /dev/tty (666)
Permissions on /dev/console (622)
Permissions on /etc/resolv.conf (644)
Permissions on /usr/dt/bin files

Check the bold commands and filenames on the left side of the list
below and compare the output on your machine with the corresponding
information on the right.

df    -     Check for full filesystems.
hostname    -    Should return hostname of machine.
host <hostname>    -    Should return fully qualified machine name and
IP address.
host <IP address>    -    Should return fully qualified machine name
and IP address.
uname -n    -    Should return hostname.
ping <hostname>    -    Should be pingable, check for packet loss.
ping <IP address>    -    Should be pingable, check for packet loss.
host loopback    -    Should return localhost is 127.0.0.1.
host 127.0.0.1    -    Should return localhost is 127.0.0.1.
ping loopback    -    Should be able to ping - check for packet loss.
ping 127.0.0.1    -    Should be able to ping - check for packet loss.
/etc/hosts    -    Check for duplicate/erroneous entries and
permissions.
/etc/resolv.conf    -    Nameserver should be pingable.
/etc/netsvc.conf - This file may or may not be present, check for
typing errors. In this file, nsorder should be hosts=local,bind
/etc/X0.hosts - This file may or may not be present, if it is move it
to X0.hosts.old.
netstat -in - Check to ensure no interfaces have an "*" (asterisk).
lssrc -s inetd - Should be active.
lssrc -s portmap - Should be active.
lssrc -g tcpip - Check to see what TCP/IP deamons are running.

If checking the preceding commands or files does not resolve the
problem, look for errors in the following files:

/var/dt/Xerrors
$HOME/.dt/startlog
$HOME/.dt/errorlog

If no errors exist in the preceding files, your system may have an
environmental setting that is prohibiting the login. Check the
following files:

/etc/environment
/etc/profile
$HOME/.dtprofile
$HOME/.kshrc
$HOME/.login
$HOME/.cshrc
echo $LIBPATH - Should report nothing.
echo $MANPATH - Should report nothing.

CDE Quick Reference Guide

--------------------------------------------------------------------------------
Starting CDE
Minimum filesets
Important files
Keep CDE from coming up on the console
Make CDE read your .profile
Important permissions
Setting the display
Connection refused

--------------------------------------------------------------------------------

Starting CDE
To start CDE, enter:

/usr/dt/bin/dtconfig -e
/etc/rc.dt;exit

To stop CDE, enter:
         /usr/dt/bin/dtconfig -d

To reset CDE, enter:
         /usr/dt/bin/dtconfig - reset

To force a logout, enter:
        ps -ef | grep dtsession kill -9 <pid>

--------------------------------------------------------------------------------

Minimum filesets
Check for the minimum filesets needed on your system, enter lslpp -l
X11.Dt*

        X11.Dt.ToolTalk --  AIX CDE ToolTalk Support
        X11.Dt.bitmaps  --  AIX CDE Bitmaps
        X11.Dt.compat   --  AIX CDE Compatibility
        X11.Dt.helpinfo --  AIX CDE Help Files and Volumes
        X11.Dt.helpmin  --  AIX CDE Minimum Help Files
        X11.Dt.helprun  --  AIX CDE Runtime Help
        X11.Dt.lib      --  AIX CDE Runtime Libraries
        X11.Dt.rte      --  AIX Common Desktop Environment

--------------------------------------------------------------------------------

Important files

/var/dt/Xerrors
$HOME/.dt/errorlog
$HOME/.dt/startlog
/usr/dt/bin/dtlogin --  The login server and display manager
/usr/dt/bin/dtgreet --  Displays a login screen for a display
/usr/dt/bin/dtchooser --  Displays a chooser screen for a display
/usr/dt/bin/Xsession --  Starts a desktop session
/usr/dt/config/Xfailsafe -- Starts a failsafe session
/usr/dt/config/Xconfig --  Login server configuration file
/usr/dt/config/Xservers --   Login server display description file
/usr/dt/config/Xaccess --   Login server access description file
/usr/dt/config/language/Xresources -- Display layout resources
/usr/dt/config/Xsetup --  Display setup file
/usr/dt/config/Xstartup --  Pre-session startup file
/usr/dt/config/Xreset --  Post-session reset file
/var/dt/Xpid--   Process ID of the login server
/var/dt/Xerrors --   Error log file of the login server

--------------------------------------------------------------------------------

Keep CDE from coming up on the console
Enter:
        cp /usr/dt/config/Xservers /etc/dt/config/xservers

Enter:
        chmod 755 /etc/dt/config/xservers

Using your preferred editor, open /etc/dt/config/xservers and comment
out the following line:
:0 Local local@console /usr/lpp/X11/defaults/xserverrc -T -force :0

After saving your changes, enter:
        /usr/dt/bin/dtconfig -reset

--------------------------------------------------------------------------------

Make CDE read your .profile
Uncomment DTSOURCEPROFILE = TRUE in .dtprofile, or
/usr/dt/config/sys.dtprofile for global.

To ensure that all dtterm/aixterms source the .profile, use your
preferred editor to open /etc/dt/config/$LANG/sys.resources and add
the following line:
        *loginShell:  true

Logout

Login

Invoke dtterm from front panel.

To have your kshrc sourced, insert the following line in .profile
        export ENV=$HOME/.kshrc

--------------------------------------------------------------------------------

Important permissions
Permissions on /dev/null (666)
Permissions on /dev/lft0 (666)
Permissions on /dev/tty (666)
Permissions on /dev/console (622)
Permissions of /usr/dt/bin files
Permissions on /var/tmp (666)
Permissions on /var/dt/tmp (666)
Permissions on /etc/hosts (664)

--------------------------------------------------------------------------------

Setting Display
        export DISPLAY=[machine.name]:0

or

        export DISPLAY=[ip.address.of.machine]:0

--------------------------------------------------------------------------------

Connection Refused
Enter:
        xhost +

Enter:
        xhost + <hostname to allow>

To make this permanent, add a line to the /etc/X0.hosts file.
Add the <hostname> you want to allow to this file.



 Sun, 06 Feb 2005 16:34:23 GMT   
 
   [ 1 post ] 

Similar Threads

1. man search paths not working anymore

2. reboot with Ctrl-Alt-Del not working anymore

3. Syslogd not working anymore

4. wvdial via telnet does not work anymore

5. Samba not working anymore!

6. ppp not working anymore

7. acl lists not working in Squid anymore

8. Problem: NFS not working anymore!

9. Ethernet works PPP-ON does not (anymore)

10. ^C is not working anymore


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software