06-29-2004
CDE login vs. X-windows
Hi, I'm new to the whole X-windows environment.
Need help please..
Believe it or not- I have a licensed "Reflection".
I use the XDMCP host, and I can see 4 servers there.
2 of the servers are aix servers: one is ver 4.3, the other one is ver 5.
When I open a session to the aix4.3 a large login screen appears, and after login the CDE is initiating. I manage to logon successfully -and get the CDE desktop.
On the other machine (AIX ver 5) when I open a session - a poor x-windows login screen appears, and after logging in I get the xclock and an X-terminal.
How do I start the CDE on the AIX ver 5?
I installed and started the dt. (/etc/rc.dt start).
What should I do next?
BTW - It might be a clue: I started the xdm on the Aix 5 and it appeared on the XDMCP host selection but all the other servers say how many users are logged in and the load average, and this one just says : "willing to manage" instead.
Also - I found out that on the other AIX (The ver 4.3) the xdm is not started but I can still start a session.
What's going on????
10 More Discussions You Might Find Interesting
1. HP-UX
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies
2. HP-UX
I've just completed a fresh install of HP-UX 11.0 on my 712/80 and everything starts up fine until it gets to the point where X kicks off and I believe at this point is supposed to launch into the CDE login.
It just sits there on the blank X screen with the X cursor for a minute or so then BEEPS... (9 Replies)
Discussion started by: ErikTheHAck
9 Replies
3. Solaris
Hi ,
I have SunBlade 150 Workstation (Solaris 9), I installed the OS again then when I try to login to any server using ( Options > Remote Login > Enter Host Name)
after I entered any host name nothing happened just white page for 2 or 3 mintues then the login screen reseted to the local... (4 Replies)
Discussion started by: adel8483
4 Replies
4. UNIX for Advanced & Expert Users
I'm having problem with the CDE pre login banner.
I configured the c/usr/dt/config/C/Xresources file to add my warning message:
Dtlogin*greeting.labelString: My Banner
I then modified the Dtlogin*greeting*fontList to display the message in smaller text. This did not work.
... (1 Reply)
Discussion started by: equismorio
1 Replies
5. Solaris
Dear All
I am in a strange situation where I have install the Solaris 10 5/08 OS on Netra 1280 server. When I connect it through my laptop so that I can take the GUI from xmanager. When I try to login as root or any other users also through Java Destop Environment which accepted it after few... (3 Replies)
Discussion started by: girish.batra
3 Replies
6. HP-UX
Dear Forum,
I had this problem initially with HPUX 11.23, all users including root could not login via CDE or telnet. Then after some workarounds, it resolved by resetting root password via console login. After enabling back all users to login normally (via CDE or telnet), only root can not... (4 Replies)
Discussion started by: irda
4 Replies
7. AIX
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
I... (0 Replies)
Discussion started by: semso
0 Replies
8. UNIX for Dummies Questions & Answers
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
... (4 Replies)
Discussion started by: semso
4 Replies
9. HP-UX
Hi all,
I canīt get a remote desktop login through CDE only with root user.
There are messages in the Xerror file:
/usr/bin/X11/xset: bad font path element (#0), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font... (5 Replies)
Discussion started by: the0m3n
5 Replies
10. HP-UX
Hi all,
I'm installing a HP r2660 machine with HP-UX 11.23 (this version fixed by customer's product) and I've troubles using the VGA console as workstation display.
At first it worked just as TEXT console, then I fixed /etc/dt/config/Xservers and now I've the CDE prompt for login.
... (5 Replies)
Discussion started by: larry100
5 Replies
LEARN ABOUT OPENDARWIN
xdm.options
xdm.options(5) File Formats Manual xdm.options(5)
NAME
xdm.options - configuration options for the X display manager
DESCRIPTION
/etc/X11/xdm/xdm.options contains a set of flags that determine some of the behavior of the X display manager xdm(1x). Most of xdm's
behavior is customized through other files; consult the xdm manual page if this manual page does not describe the behavior you want to
alter.
/etc/X11/xdm/xdm.options may contain comments, which begin with a hash mark ('#') and end at the next newline, just like comments in shell
scripts. The rest of the file consists of options which are expressed as words separated by hyphens, with only one option per line.
Options are enabled by simply placing them in the file; they are disabled by prefixing the option name with 'no-'.
Available options are:
ignore-nologin
Normally, if the nologin(5) file exists, its contents will be displayed using xmessage(1x) (if xmessage is available), and the user
will be returned to the xdm login screen after xmessage is dismissed instead of starting the X session. If this option is enabled,
xdm starts a session as usual (after xmessage is dismissed, if xmessage is available and the nologin file exists). This behavior is
disabled by default: nologin is heeded, not ignored.
restart-on-upgrade
Enable this option with caution on 'production' machines; it causes the daemon to be stopped and restarted on upgrade, even if the
process has children (which means it is managing X sessions). Typically when a package that contains a daemon is being installed or
upgraded, its maintainer scripts stop a running daemon process before installing the new binary, and restart it after the new binary
is installed. Stopping xdm causes immediate termination of any sessions it manages; in some situations this could be an unwelcome
surprise (for instance, for remote xdm users who had no idea the administrator was performing system maintenance). On the other
hand, for machines that stay up for long periods of time, leaving the old daemon running can be a bad idea if the new version has,
for instance, a fix for a security vulnerability (overwriting xdm's executable on the file system has no effect on the copy of xdm
in memory). The xdm package's pre-removal script checks to see if the xdm process has any children; if it does, it is possible that
someone's session would be killed by stopping xdm, so a warning is issued and an opportunity to abort the upgrade of xdm is pro-
vided. Furthermore, restarting xdm on upgrade can be surprising, because a locally-managed X server can change the active VT even
while other packages are continuing to upgrade. If, by intent or accident, the X server does not honor the key sequence to switch
VTs back to a virtual console, this can be undesirable. This behavior is disabled by default: xdm will be not be stopped or started
during an upgrade of its package; the administrator will have to do so by hand (with invoke-rc.d xdm restart or by rebooting the
system) before the newly installed xdm binary is used.
start-on-install
Enable this option with caution; it causes the xdm daemon to be started immediately after the package is installed. See the above
entry regarding restart-on-upgrade for other caveats regarding the consequences of starting the xdm daemon during package manage-
ment. This behavior is disabled by default: xdm will not be started when it is installed. Changing this setting can affect future
installs if the package is removed, but not purged (which removes 'conffiles', including xdm.options).
use-sessreg
This option causes the /etc/X11/xdm/Xreset script to call the sessreg(1x) program to register X sessions managed by xdm in the
utmp(5) and wtmp(5) files. If it is disabled, the utmp and wtmp files will have no record of xdm sessions. This behavior is
enabled by default; sessreg will be used.
Users of older versions of the Debian system should note that the 'run-xconsole' option has been removed. The shell script named
/etc/X11/xdm/Xreset can be edited to disable or modify the running of xconsole on the xdm greeter screen; see xdm(1x) for more information.
AUTHORS
Stephen Early, Mark Eichin, and Branden Robinson customized xdm's startup and reset scripts and package maintainer scripts to implement the
functionality described above. This manual page was written by Branden Robinson.
SEE ALSO
sessreg(1x), xmessage(1x), xdm(1x), nologin(5), utmp(5), wtmp(5)
Debian Project 2004-10-31 xdm.options(5)