Path: utzoo!attcan!uunet!decwrl!sgi!betsy@vesuvius.esd.sgi.com
From: betsy@vesuvius.esd.sgi.com (Betsy Zeller)
Newsgroups: comp.sys.sgi
Subject: Re: workspace shell sdtout
Message-ID: <63940@sgi.sgi.com>
Date: 12 Jul 90 17:52:53 GMT
References: <9007100212.AA02012@mcirps2.med.nyu.edu>
Sender: betsy@vesuvius.esd.sgi.com
Reply-To: betsy@vesuvius.UUCP (Betsy Zeller)
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 22

In article <9007100212.AA02012@mcirps2.med.nyu.edu> dean@MCIRPS2.MED.NYU.EDU writes:
>
>when workspace is started in a login or user.ps, all stderr and stdout
>is lost.(or goes somplace I don't know about right now).
>
>I have to start it in a shell to capture the error output from the cmd open
>and other rules that involve shells.
>
>This property is sub-optimal.
>

The preferred method of having workspace start up when you log in is to
use the system manager, open the user tool, select the users icon, and
set workspace 'on' in the appropriate spot (by selecting a button). 
This will ensure that workspace starts up whenever that user logs on. When
workspace is started via this mechanism, these errors  go to the
console window, which is preferable to having them disappear into
hyperspace. 

Hope this helps.
Betsy Zeller
betsy@sgi.com