On Fri, Oct 25, 2002 at 07:10:35AM -0400, Kevin Coyner wrote:
>
>
> On Fri, Oct 25, 2002 at 09:25:05AM +0100, Rupert wrote......
>
> > On Thu, 24 Oct 2002 21:49:07 -0400
> > Kevin Coyner <kevin@rustybear.com> wrote:
> >
> > > But in trying Xnest, I ran into a problem ... as per the man, I tried
> > > the simple startup command of 'Xnest :1'. It does bring up a next, but
> > > I can't do anything with it. No clicks and no buttons work.
> >
> > You need to run something to respond to your clicking, like a window
> > manager. Try this:
> >
> > Xnest :1&
> > DISPLAY=:1 ion&
>
> Hmmm ... this still isn't working for me. I tried:
>
> Xnest :1&
> ion -display :1&
>
> and while I get the Xnest, I don't get the xterm to show up within the
> Xnest. The err msg is ...
>
> sakura:~$ ion -display :1&
> [2] 14609
> sakura:~$ AUDIT: Fri Oct 25 06:50:55 2002: 14577 Xnest: client 1
> rejected from local host
> Xlib: connection to ":1.0" refused by server
> Xlib: Client is not authorized to connect to Server
> ion: Could not connect to X display ':1'
If it's just for fooling around, then you could try:
Xnest -ac -nolisten tcp :1 &
since -ac disables all access control, but "-nolisten tcp" should stop
it listening on the network. The end result should be that only users
with access to your machine can access the new X server.
HTH
--
Karl E. Jørgensen
karl@jorgensen.com http://karl.jorgensen.com
==== Today's fortune:
Nothing is illegal if one hundred businessmen decide to do it.
-- Andrew Young
Attachment:
pgpppMxgL5aNy.pgp
Description: PGP signature