NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/unix/sysv386/17424

Text File | 1992-12-15 | 3.4 KB | 83 lines

Newsgroups: comp.unix.sysv386
Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsk!cbnewsj!dwex
From: [e-mail] (david.e.wexelblat)
Subject: Re: configuring xdm on Dell 2.2
Organization: AT&T
Date: Tue, 15 Dec 1992 21:27:49 GMT
Message-ID: <[e-mail]>
References: <[e-mail]> <[e-mail]>
Lines: 72

In article <[e-mail]> [e-mail] (Sam Neely) writes:
> In article <[e-mail]> [e-mail] (Mark Solsman) writes:
> >Hello-
> >
> >Seems that I have been elected to try and figure this out :(
> >
> >Seems that DELL did a very nice job of configuring the xdm for you, they
> >even set up all of your files for you!!! :)
> >
> >However, I must have missed where it tells you how to get the thing to execute
> >upon startup.  Am I supposed to place it in /etc/rc2.d ??  Does anyone use this?
>
> Just a guess -- I'm sure you'll get a more authoritative answer from
> someone else --  I would think that you'd have to disable the ttymon
> process on /dev/console and replace it with the xdm.  sacadm(1) comes
> to mind as a place to look.
>

Unless Dell has done something odd, there's no reason to do this.  The
X server runs on a VT, not on the console.  What I use for Microport SVR4
(which I assume will work for Dell as well) is to have a script in
/etc/init.d, called Xdm.  Model it on the other files, with a start and
stop case.  The start case has essentially the following:

    if [ ! -f <xdm-lib-dir>/.badexit ]
    then
        touch <xdm-lib-dir>/.badexit
        xdm
    fi

And the stop case has

    kill `cat <xdm-lib-dir>/xdm-pid`
    rm -f <xdm-lib-dir>/.badexit

Then link this to /etc/rc2.d/S??xdm and /etc/rc0.d/K??xdm.  For ?? I used
something in the 80's.

Sorry I can't send the real script - it's on my machine at home, and I can't
get to it because the phone lines are still out due to the storm last
weekend.

You can probably ignore the .badexit stuff, unless you are doing server
development (as I am :->).  In that case, it's a godsend, keeping xdm from
looping forever, trying to start the server, in those rare (;->) instances
where you manage to bolux up the server.

> >Thanks in advance!
> >
> >--
> >Mark Solsman                                 Building 1, Code 5160
> >United States Naval Research Laboratory      [e-mail]
> >Washington, DC                               [phone]
> --
> Sam Neely, CompuServe Incorporated                  [phone] (voice)
> 5000 Arlington Centre Blvd, Columbus, OH  43220     [phone] (FAX)
> Electronic Mail:  InfoPlex: >CSI:SAM      Internet: [e-mail]
> To err is human, to forgive is against company policy

One note for xdm users - unless Dell has fixed a rather nasty little bug
in xdm (which I doubt), you may not be able to use XDM-AUTHORIZATION-1
authentication (it may screw up boards on your bus, or even lock up the bus).
I sent the fix to MIT, but it has yet to appear in a public fix (if anyone
wants it, the fix is in XFree86, or I can send you a source patch - send
me email).

--
David Wexelblat <[e-mail]>  [phone]
AT&T Bell Laboratories, 200 Laurel Ave - 3F-428, Middletown, NJ  07748

"The meaning of life?  That's simple.  Try to be happy, try not to hurt
 other people, and hope to fall in love."  -- Mallory Keaton