Displaying 4 results from an estimated 4 matches for "stop_listening".
2002 Feb 04
1
forkoff()
...e detaching and some of the hang-on-exit options work correctly I
need a way to force a channel closed and to do it in way that is
correct wrt to the SSHv2 protocol. The forkoff() function below does
that, I think, but it would be nice to have confirmation.
Comments?
Nico
static
void
forkoff(int stop_listening, int detach)
{
pid_t pid;
int fd;
Channel *c;
/* Restore tty modes. */
leave_raw_mode();
/* Stop listening for new connections. */
if (stop_listening)
channel_stop_listening();
fprintf(stderr, "Forking off into the background - %s",
stop_listening ? "no longer listenin...
2002 Feb 01
1
FEATURE: -f -f - fork after successful open of fwd port/display/agent
...eived a window change signal which has
* not yet been processed. This will cause a message indicating the new
@@ -1007,6 +1010,80 @@
/*********/
+/*
+ * Detach the program (continue to serve connections,
+ * but put in background and no more new connections).
+ */
+static
+void
+forkoff(int stop_listening, int detach)
+{
+ pid_t pid;
+ int fd;
+ Channel *c;
+
+ /* Restore tty modes. */
+ leave_raw_mode();
+
+ /* Stop listening for new connections. */
+ if (stop_listening)
+ channel_stop_listening();
+
+ fprintf(stderr, "Forking off into the background - %s",
+ stop_listening ? "no l...
2002 Feb 05
0
New forkoff() and chan_wont_read/write() API
...5_ubsw_experimental.6/clientloop.c Tue, 05 Feb 2002 11:16:16 -0500 willian (OpenSSH/j/41_clientloop 1.1.2.7 644)
@@ -1007,6 +1051,81 @@
/*********/
+/*
+ * Detach the program (continue to serve connections,
+ * but put in background and no more new connections).
+ */
+static
+void
+forkoff(int stop_listening, int detach)
+{
+ pid_t pid;
+ int fd;
+ Channel *c;
+
+ /* Restore tty modes. */
+ leave_raw_mode();
+
+ /* Stop listening for new connections. */
+ if (stop_listening)
+ channel_stop_listening();
+
+ fprintf(stderr, "Forking off into the background - %s, %s",
+ stop_listening ? "...
2002 Jan 11
1
X11 forwarding, -f, error handling
I'd like a feature whereby ssh puts itself in the background after the
first successful X11 (or other port) forwarding.
The reason for this is simple: error handling.
If the application fails to open the X display and exits, then the
client can still exit with the application's exit code. But if the
application opens the X display successfully, then it can just display
any errors by