Angus Henderson (angus++at++death.reading.sgi.com)
Wed, 26 Oct 1994 09:51:47 +0000
Then every time you want to issue a setmon command and get back to a fully
working window manager do something like...
setenv DISPLAY :0.0
/usr/gfx/setmon -S 4++at++640x480_60
/usr/gfx/stopgfx
/usr/gfx/startgfx
touch /etc/autologin.on
It works for us - Tom Fuke worked it out.
ANgus
On Oct 25, 6:04pm, Richard Gallery wrote:
> Subject: How to start up a remote session
> Hi
>
> This is not strictly speaking a Performer question, but
> I would expect that those of you using an MCO might
> have encountered this issue.
>
> So, I've got an application that uses Performer to drive the
> MCO on an Onyx. My main screen is disabled while using the MCO.
> I am able to start my
> Performer application up on my Onyx from an Indigo, using
> rsh to start up the Performer application. The problem with
> this is that I still have to log onto the Onyx to start up
> a window server on it before it will accept my Performer
> application. So what I need to be able to do is remotely start up
> a window server on the Onyx from my Indigo. I have tried
> messing round with doing an xinit directed at the Onyx from my
> Indigo, with no success (
> I did, while in a window on the Indigo logged in to the onyx,
>
> xinit -display sal:0
>
> (sal is our Onyx)
> and the system said
>
> /usr/gfx/gfxinit: Not privileged
> gfxinit: graphics initialize failed)
>
> So, I'm sure this has been done before, anyone any ideas
>
>
>
> Thanks
> Richard
>
>
>
>
>-- End of excerpt from Richard Gallery
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:36 PDT