SUMMARY: xdm start-up affects cmd/shelltool

From: Peter Koblauch (
Date: Mon Jul 08 1991 - 15:51:57 CDT

This is a great list.

Thanks to all who replied.
Thanks in particular to:
-Leonard E. Sitongia
-Bill Hart
-Gareth J. Barker
-Dave Singletary
-Mark Korinek

Here's an (abbreviated) version of initial mayday:

        When started up from the olwm root menu both shelltool/cmdtool
        come up but no shell prompt appear. Kbd input is echoed but not
        acted upon. Other DeskSet tools work fine.

        I think the problem is related to xdm.
        xdm is running as session/login manager for HP 700RX terminals
        off an SLC host.

        is started up from /etc/rc.local
        or - with similar result
        /usr/bin/X11/xdm -nodaemon &
        or - with similar result
        sh -c "/usr/bin/X11/xdm -nodaemon &"

        If started up from console eg sh -c "/usr/bin/X11/xdm -nodaemon&"
        instead of from within /etc/rc.local everything is fine,
        but really would like to have xdm started automatically during boot.

        When tools hang users's .xsessionlog has message
        "ttysw-TIOCSPGRP: Interrupted system call"

        Both tools may be started up from another window, say xterm,
        without any problems, regardless of whether xterm is a decendant of xdm.

        Should xdm be started up differently or from another place
        (/etc/ttytab?) in order to have a controlling terminal
        to pass on to descendants?

Problem is related to some DeskSet clients needing a
controlling terminal passed on from parent.
When started up from (an orphaned) xdm, client doesn't have one.
The clients that I know of are: cmdtool (=shelltool), and dbxtool.

As an aside,- does anybody know of an automated way of starting up xdm
                (-nodaemon) during booting so that it still keeps its
                controlling terminal?

wrap offending tool in setsid. # setsid(8)
1) (from line in .xsession)
   setsid -b cmdtool
2) (from line in .openwin-menu)
    "Command Tool..." DEFAULT exec setsid cmdtool
3) apply instructions given in man setsid(8) to offending client.
   This -3)- has has worked fine at my installation for some time.

Peter Koblauch,
HP Panacom,
Waterloo, Ontario

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:21 CDT