Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!mentor.cc.purdue.edu!mace.cc.purdue.edu!abe
From: abe@mace.cc.purdue.edu (Vic Abell)
Newsgroups: comp.sys.next
Subject: Re: csh & the NeXTs
Message-ID: <1765@mace.cc.purdue.edu>
Date: 17 Feb 89 21:24:24 GMT
References: <17953@vax5.CIT.CORNELL.EDU> <1889@csun.edu> <451@garcon.cso.uiuc.edu>
Distribution: na
Organization: Purdue University
Lines: 18

In article <451@garcon.cso.uiuc.edu>, dorner@pequod.cso.uiuc.edu
(Steve Dorner) writes about a way to create a program that will be
launched at login time instead of the Workspace manager.  That program
can initialize, call the WM, and do wrapup functions.

Steve's approach works nicely.  Coupled with Christopher Lane's bright
program, it enables one to have a poor man's screen dimmer/brightener
at logoff/logon time.

There's one "gotcha": the Workspace manager that the program runs loses
contact with the console and you cannot use the Console item of its Utilities
submenu.  I'm a bit surprised, since that WM process is started by a
fork/execl and should inherit the file descriptors of the program that
started it.

How does the WM access the console?

Vic Abell