ntpd: explain why scripts can be run in quick succession

[oweals/busybox.git] / networking / telnetd.c

diff --git a/networking/telnetd.c b/networking/telnetd.c
index 2a0ace5cb79ce4dc50f7733af86e5d8fcc9c16b1..b0a1cc4d8632a71d6713aa967f98b411827b4c9c 100644 (file)
--- a/networking/telnetd.c
+++ b/networking/telnetd.c
@@ -288,7 +288,7 @@ make_new_session(
                /*ts->size2 = 0;*/
        }
 
-       fflush(NULL); /* flush all streams */
+       fflush_all();
        pid = vfork(); /* NOMMU-friendly */
        if (pid < 0) {
                free(ts);
@@ -331,7 +331,7 @@ make_new_session(
        /*termbuf.c_lflag &= ~ICANON;*/
        tcsetattr_stdin_TCSANOW(&termbuf);
 
-       /* Uses FILE-based I/O to stdout, but does fflush(stdout),
+       /* Uses FILE-based I/O to stdout, but does fflush_all(),
         * so should be safe with vfork.
         * I fear, though, that some users will have ridiculously big
         * issue files, and they may block writing to fd 1,
@@ -562,13 +562,15 @@ int telnetd_main(int argc UNUSED_PARAM, char **argv)
        }
 
        {
-               struct timeval tv;
                struct timeval *tv_ptr = NULL;
+#if ENABLE_FEATURE_TELNETD_INETD_WAIT
+               struct timeval tv;
                if ((opt & OPT_WAIT) && !G.sessions) {
                        tv.tv_sec = sec_linger;
                        tv.tv_usec = 0;
                        tv_ptr = &tv;
                }
+#endif
                count = select(G.maxfd + 1, &rdfdset, &wrfdset, NULL, tv_ptr);
        }
        if (count == 0) /* "telnetd -w SEC" timed out */