- djm@cvs.openbsd.org 2011/05/08 12:52:01

     [PROTOCOL.mux clientloop.c clientloop.h mux.c]
     improve our behaviour when TTY allocation fails: if we are in
     RequestTTY=auto mode (the default), then do not treat at TTY
     allocation error as fatal but rather just restore the local TTY
     to cooked mode and continue. This is more graceful on devices that
     never allocate TTYs.

     If RequestTTY is set to "yes" or "force", then failure to allocate
     a TTY is fatal.

     ok markus@

1 files changed, 3 insertions, 1 deletions

diff --git a/clientloop.h b/clientloop.h
index 37d072906..ad588d14d 100644
--- a/clientloop.h
+++ b/clientloop.h
@@ -1,4 +1,4 @@
-/* $OpenBSD: clientloop.h,v 1.26 2011/04/17 22:42:41 djm Exp $ */
+/* $OpenBSD: clientloop.h,v 1.27 2011/05/08 12:52:01 djm Exp $ */
 
 /*
  * Author: Tatu Ylonen <ylo@cs.hut.fi>
@@ -70,3 +70,5 @@ void	 client_register_global_confirm(global_confirm_cb *, void *);
 void    muxserver_listen(void);
 void    muxclient(const char *);
 void    mux_exit_message(Channel *, int);
+void    mux_tty_alloc_failed(Channel *);
+