Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpcvlx.cv.hp.com!peter
From: peter@hpcvlx.cv.hp.com. (Peter Robinson)
Newsgroups: comp.sys.hp
Subject: Re: xdm on HP-4xx?
Message-ID: <101950239@hpcvlx.cv.hp.com.>
Date: 22 Jun 91 01:40:41 GMT
References: <KJETIL.SVARSTAD.91Jun19112251@mek.delab.sintef.no>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 31

>/ hpcvlx.cv.hp.com:comp.sys.hp / Kjetil.Svarstad@delab.sintef.no (Kjetil Svarstad) /  2:22 am  Jun 19, 1991 /
>
> I have set up the configuration files for xdm in
> /usr/lib/X11/xdm, and I have tried to start it in /etc/inittab as a
> respawn process at run-level 2 with the -nodaemon switch. 

This is an acceptable configuration. For some reason the xdm process is
aborting before it gets very far. Try running it by hand (as root) with
debugging turned on and see if anything is obvious...

	xdm -debug 1 


> 	 Should xdm be started in /etc/inittab at all, and how
> should it be done? Or should it be started as a daemon in /etc/rc, and
> if such is the case, how?

You can do it either way. Using inittab has the advantage that if the xdm
master daemon dies for some reason it is automatically restarted and you are
not left with a bunch of dead displays. 

Using /etc/rc is more traditional for starting daemons and is typically
easier to understand for many than inittab. There are many examples in
/etc/rc to follow. They usually check if the executable is available and if
so, print out a message and then run it. Create a little function for xdm
and invoke it in localrc().


Peter Robinson
HP ITO
Corvallis, OR