Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!sdd.hp.com!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!usc!elroy.jpl.nasa.gov!ucla-cs!ucla-mic!pita.cns.ucla.edu!scott From: scott@pita.cns.ucla.edu (Scott Burris) Subject: Re: xdm and login Message-ID: <scott.722536414@pita.cns.ucla.edu> Keywords: xdm /etc/ttys login Nntp-Posting-Host: pita.cns.ucla.edu References: <1992Nov23.154921.29674@Urmel.Informatik.RWTH-Aachen.DE> Date: 23 Nov 92 10:47:27 PST Lines: 34 kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: >I'm looking for a method to use xdm to come up on my system permanently >in a fashion similar to the way it's done on most systems, e.g. Ultrix: I'm running with xdm permanently running now. Modify /etc/ttys to run xdm instead of getty on the console. Next, modify your xdm-config file to contain the following: DisplayManager.daemonMode: false This prevents xdm from detaching itself as a daemon. If you fail to do this, init forks off many many copies of xdm, all of which try to start up X -- not a pretty sight, let me tell you from my own experience. That's it. I did see a note from someone a while ago with a recommendation to start xdm from a shell script something like this: #! /bin/sh xdm stty raw sleep 99999999 For some reason, this didn't work correctly for me. I've had no problems so far with the first method. -- ---------- Scott Burris UCLA Campus Network Services cnetslb@oac.ucla.edu (310) 206-4860 - OR - scott@pita.cns.ucla.edu