Lines Matching +full:multi +full:- +full:master

2 ControlMaster connection-sharing.
5 master. This will cause ssh(1) to listen on a Unix domain socket for
20 requesting the master terminate itself fall in to this category.
58 to connect to a master that speaks an unsupported protocol version.
109 non-multiplexed ssh(1) connection. Two additional cases that the
113 A master may also send a MUX_S_TTY_ALLOC_FAIL before MUX_S_EXIT_MESSAGE
120 3. Requesting passenger-mode stdio forwarding
122 A client may request the master to establish a stdio forwarding:
151 5. Remotely terminating a master
153 A client may request that a master terminate immediately:
162 A client may request the master to establish a port forward:
174 If listen port is (unsigned int) -2, then the listen host is treated as
177 If connect port is (unsigned int) -2, then the connect host is treated
191 A client may request the master to close a port forward:
206 A client may request the master to stop accepting new multiplexing requests
223 When a mux master receives this message, it will reply with a
235 	byte[packet length - 2] ...
237 The mux master will accept most connection messages and global requests,
287 XXX server->client error/warning notifications
290 XXX extensions for multi-agent
291 XXX extensions for multi-X11
292 XXX session inspection via master