I have Sol8 loaded on Ultra10. All of a sudden, whenever anyone including "root" tries to login thru CDE, the sytems window hangs showing CDE 1.4. Then i am left with no option but to grep Xsun; and kill its pid. Is there any solution.... Please help asap. thanks Rajeev

CORE CDE components: I. Login Manager - Where you see the login screen. II. The Session Manager III. The Workspace Manager Sounds like your having problems at the session manager. Double check that it is happing to everyone. If it is look at the system wide varibles. Following is a detailed description of what happens: When a user logs in using the Login Screen provided by the Login Manager, the Session Manager /usr/dt/bin/Xsession command is started. The Xsession command performs the following actions: 1. /usr/dt/bin/Xsession reads and executes the .dtprofile script under the users' home directory. 2. any scripts under /usr/dt/config/Xsession.d are read and executed. 3. Welcome message displayed 4. Sets up desktop search path using /usr/dt/bin/dtsearchpath command 5. Locates the availble applications using the /usr/dt/bin/dtappgather command by searching through the desktop search paths. 6. Reads and executes the login initialization file (.login or .profile) if the DTSOURCEPROFILE variable in the .dtprofile is set to true 7. Starts the ToolTalk messaging system 8. /usr/dt/bin/dtsession takes over startup process 9. Loads the system default session resource and merges them with any system wide defaults 10. starts the color server specified by sys.resources file 11. Starts the workspace manager 12. Starts the session applications. Any applications identified by the /etc/dt/config/C/sys.session file or the /usr/dt/config/C/sys.session file are started.

Rajeev, Just had the same problem with a 2.6 machine. I strongly suggest that rather than grep for Xsun and killing that process you should got to /etc/init.d and run dtlogin -stop! If you kill the Xsun process directly you will leave orphaned ttsession processes running all over the place that will build up over time which will only add to future problems.

Try commenting out the DTSOURCEPROFILE=TRUE in the ~/.dtprofile. If CDE starts, then it means there is a statement in the .profile which is not CDE safe. In the .profile you can test for $DT variable being set. Place the non CDE friendly commands within a [ ! $DT ] if block.

if anyone can help me with this. beofore CDE we used to take input from user on command prompt regarding TERMINAL type and Project name and set the user to that environment. as to my info we cannot take input fm user at login time in CDE.That means cannot use .login fr the statement "source /mydir/askquestions". the only option is to put it in .cshrc so that everytime when a terminal opens in CDE environment it asks fr the iput. BUT this has a problem with commands like which and top as they read .cshrc as well to find paths. can anyone tell how to solve this riddle. and which files does a terminal read when it is closed. lilke when it is opened it reads .cshrcs and .login or .profile. but what at logout time. And yes i'm in cshell environment. Thanks fr any feed back.