Re: [vincent@xxxxxxxxxx: Re: Bug#205685: clone corruption]

[Philippe Troin <phil@xxxxxxxx>]

Clint Adams <schizo@xxxxxxxxxx> writes:

> I haven't used clone before this, but I can reproduce the behavior
> described below.
> 
> ----- Forwarded message from Vincent Lefevre <vincent@xxxxxxxxxx> -----
> 
> On 2004-07-17 16:10:04 -0400, Clint Adams wrote:
> > Hmm, is this still a problem?
> 
> clone doesn't even work any longer. For instance:
> 
> In the first terminal:
> 
> greux:~> exec zsh -f
> greux% tty
> /dev/pts/240
> greux% foo=bar
> greux% echo $foo
> bar
> greux% zmodload zsh/clone
> greux% clone /dev/pts/241
> greux% 
> 
> In the second terminal:
> 
> greux:~> exec zsh -f
> greux% tty
> /dev/pts/241
> greux% clone: could not make /dev/pts/241 my controlling tty, job control disabled
> greux% echo $foo
> 
> greux% 
> 
> (The message "clone: could not make..." appeared just after executing
> "clone /dev/pts/241" in the first terminal.)
> 
> ----- End forwarded message -----

Probably two shells running on the same terminal, this is NOT
supported and can only lead to bad results.

The only way to use clone is to start it on an unused terminal,
started with eg:

  xterm -e sh -c 'trap : INT QUIT TSTP; tty; while :; do sleep 100000000; done'

or on an unused virtual console.

Phil.