Re: Odd ctrl-s problem.

you can just use:

    idlestring "^Q";

(a literal carat and Q - two characters)

conserver should only be sending characters it's told to send (the only
exception i can think of is when it's doing telnet option negotiation).
the ssh command is being run withing a pseudo-tty and those layers
*might* be doing something.  for example, there could be things buried
in shell startup scripts (since conserver cranks off a /bin/sh to
actually run the command) or some unexpected stty setting on the
pseudo-tty.

i'm lacking on any concrete ideas, however.  well, aside from using
truss/strace and seeing if there are ctrl-s characters flying around.

Bryan

On Thu, Feb 07, 2008 at 10:42:44AM +0000, Peter Saunders wrote:
> Many thanks for your replies,
> 
> I still haven't got to the bottom of what actually caused it, but, it
> seems odd if was the terminal server. Its a reasonably recent event that
> conserver went live on these machines - and in the past, the terminal
> servers didn't have a connection to them from the network, so, all the
> serial traffic was silently thrown away. This is what I was expecting to
> happen during the conserver restart window. (People used to ssh to the
> terminal server only when they needed the console)
> 
> However, I think i'll change the the idlestring to contain ^q - so in
> the event of a restart causing it again, at least after 5 minutes of
> inactivity, conserver would sent a ctrl-q to it again. (Assuming I can
> get it to do this?)
> 
> Cheers
> Pete