HP-UX

The CDE login manger may repeatedly scroll these error

messages on the console:

****************************************************************

* The X-server cannot be started on display <hostname>:0...

* For details look into the file, Dtlogin.errorLogFile (default:

* /var/dt/Xerrors)

****************************************************************

****************************************************************

* Suspending Desktop Login...

* Press [Enter] for a login prompt.

* Log in. Desktop Login will resume shortly after you log out.

****************************************************************


-------
Problem is, it says this is a usb device problem on the hp site, read the fix, but it has nothign to do with me.. i tried it but didnt work, im on a c240 server that doesnt even have USB ports, im using a terminal to speak with the server.. i get this screen everytime i boot it up and i just want to get rid of it, anyway how? i dont need x-server.. heeelp!

-emp

check /etc/inittab for the default run level and modify it there ...

eehk.. What exactly do i look for in there?

this CDE login is really killing me ....i cannot figure this out..

heres the error log from Xerrors

Fatav serve error:
r:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "bylot:0.0"^M
after 0 requests (0 known processed) with 0 events remaining.^M

Fatal server error:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "bylot:0.0"^M
after 0 requests (0 known processed) with 0 events remaining.^M

Wed May 4 16:57:33 2005
error (pid 1325): Server for display bylot:0 can't be started.

Fatal server error:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "bylot:0.0"^M
after 0 requests (0 known processed) with 0 events remaining.^M

Fatal server error:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "bylot:0.0"^M
after 0 requests (0 known processed) with 0 events remaining.^M

please post your /etc/inittab entries ...

here is it

init:3:initdefault:
ioin::sysinit:/sbin/ioinitrc >/dev/console 2>&1
tape::sysinit:/sbin/mtinit > /dev/console 2>&1
muxi::sysinit:/sbin/dasetup </dev/console >/dev/console 2>&1 # mux init
stty::sysinit:/sbin/stty 9600 clocal icanon echo opost onlcr ixon icrnl ignpar </dev/systty
vxen::bootwait:/sbin/fs/vxfs/vxenablef -a
vol1::sysinit:/sbin/init.d/vxvm-sysboot </dev/console >/dev/console 2>&1 ##vxvm
vol2::sysinit:/sbin/init.d/vxvm-startup start </dev/console >/dev/console 2>&1 ##vxvm
brc1::bootwait:/sbin/bcheckrc </dev/console >/dev/console 2>&1 # fsck, etc.
link::wait:/sbin/sh -c "/sbin/rm -f /dev/syscon; \
/sbin/ln /dev/systty /dev/syscon" >/dev/console 2>&1
cprt::bootwait:/sbin/cat /etc/copyright >/dev/syscon # legal req
sqnc::wait:/sbin/rc </dev/console >/dev/console 2>&1 # system init
#powf:owerwait:/sbin/powerfail >/dev/console 2>&1 # powerfail
cons:123456:respawn:/usr/sbin/getty console console # system console
#ttp1:234:respawn:/usr/sbin/getty -h tty0p1 9600
#ttp2:234:respawn:/usr/sbin/getty -h tty0p2 9600
#ttp3:234:respawn:/usr/sbin/getty -h tty0p3 9600
#ttp4:234:respawn:/usr/sbin/getty -h tty0p4 9600
#ttp5:234:respawn:/usr/sbin/getty -h tty0p5 9600
krsd:123456:respawn:/sbin/krsd -i
sfd:123456:respawn:/sbin/sfd
#ups::respawn:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf
samd:23456:respawn:/usr/sam/lbin/samd # system mgmt daemon
ems1::bootwait:/sbin/rm -f /etc/opt/resmon/persistence/runlevel4_flag
ems2::bootwait:/sbin/cat </dev/null >/etc/opt/resmon/persistence/reboot_flag
ems3:3456:wait:/sbin/sh -c "/usr/bin/touch /etc/opt/resmon/persistence/runlevel4_flag; /usr/bin/chmod 644 /
etc/opt/resmon/persistence/runlevel4_flag"
ems4:3456:respawn:/etc/opt/resmon/lbin/p_client
~

i was wrong --- i had assumed HP-UX went the same way as Solaris and Linux ... anyways, i saw this on HP's CDE documentation ... i don't have access to an HP box so you'll have to check "man Xservers" yourself ...