Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!tektronix!sequent!mntgfx!rreed
From: rreed@mntgfx.mentor.com (Robert Reed)
Newsgroups: comp.sys.apollo
Subject: Re: some questions for the gurus.
Message-ID: <1988Sep20.112851.1047@mntgfx.mentor.com>
Date: 20 Sep 88 18:28:47 GMT
References: <8809152050.AA02337@richter.mit.edu>
Reply-To: rreed@mntgfx.UUCP (Robert Reed)
Organization: Mentor Graphics Corp., Beaverton OR
Lines: 14

krowitz@RICHTER.MIT.EDU (David Krowitz) writes:
    Actually, I believe that the SIGP command can be given a status code
    from the /sys/ins/fault.ins.{ftn c pas} file, although I understand
    that the process may not be suspended cleanly. You can use the Unix
    kill -STOP and kill -CONT commands  to suspend and restart processes.

I'm not sure this is always true, from the DOMAIN/IX csh man pages:

   Commands started in-process cannot be suspended or manipulated using
   the csh job-control facilities.

This is a restriction imposed on jobs started under an existing csh. If
the process has been started by doing a crp, even this may not be 
possible.  Do any of our comrades from Apollo know the answer to this?