Date: Sat, 13 Jan 1996 03:31:08 -0800 (PST) From: Chris Timmons <skynyrd@tahoma.cwu.edu> To: freebsd-questions@freebsd.org Subject: XF386 3.1.2B: server exits on signal 10 Message-ID: <Pine.VUL.3.91.960113032215.10433B-100000@tahoma.cwu.edu>
next in thread | raw e-mail | index | archive | help
Here's an edited version of a beta report I sent to the XFree people
regarding 3.1.2B on FreeBSD 2.1.0-R. All of a sudden, xdm can't seem to
start the server, whereas it had no problems doing so for 3.1.2A and before.
The server can be successfully started via startx however, and will run fine
that way. What is signal 10 telling me?
VERSION: 3.1.2B
XSERVER: XF86_S3
OPERATING SYSTEM: FreeBSD 2.1.0-R
I'm having a problem with XDM now on :0 after upgrading to 312B. When
the system comes up, instead of getting a nice XDM window on ttyv3, I
get (on the system console):
Jan 12 04:44:55 riffraff /kernel: pid 145: XF86_S3: uid 0: exited on signal 10
Jan 12 04:44:56 riffraff /kernel: pid 147: XF86_S3: uid 0: exited on signal 10
Jan 12 04:44:56 riffraff /kernel: pid 149: XF86_S3: uid 0: exited on signal 10
Jan 12 04:44:57 riffraff /kernel: pid 151: XF86_S3: uid 0: exited on signal 10
For the upgrade, I only applied X312BS3.tgz and X312Bupd.tgz. I used
the correct postinst.sh version to install 312B and can start up the
server fine using startx. It is only with XDM that I have a problem.
Using 3.1.2 and 3.1.2A I could get xdm to start up on ttyv4 with the
following startup files:
/etc/ttys:
ttyv0 "/usr/libexec/getty Pc" cons25 on secure
ttyv1 "/usr/libexec/getty Pc" cons25 on secure
ttyv2 "/usr/libexec/getty Pc" cons25 on secure
ttyv3 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure
/usr/X11R6/lib/X11/xdm/Xservers:
:0 local /usr/X11R6/bin/X -bpp 16
-Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.VUL.3.91.960113032215.10433B-100000>