Lines Matching refs:exec

18  *    echo $ssh->exec('pwd');
19  *    echo $ssh->exec('ls -la');
622      * @see self::exec()
634      * @see self::exec()
690      * @see self::exec()
703      * @see self::exec()
841      * Flag to request a PTY when using exec()
2787      * $ssh->exec('ping 127.0.0.1'); on a Linux host will never return and will run indefinitely.  setTimeout() makes it so it'll timeout.
2829     public function exec($command, callable $callback = null)
2840         //    throw new \RuntimeException('If you want to run multiple exec()\'s you will need to disable (and re-enable if appropriate) a PTY for each one.');
2871         // down.  the one place where it might be desirable is if you're doing something like \phpseclib3\Net\SSH2::exec('ping localhost &').
2872         // with a pty-req SSH_MSG_CHANNEL_REQUEST, exec() will return immediately and the ping process will then
2873         // then immediately terminate.  without such a request exec() will loop indefinitely.  the ping process won't end but
2883             'exec',
3136      * an active subsystem, the exec pty, and, lastly, the shell. If using multiple interactive
3198      * an active subsystem, the exec pty, and, lastly, the shell. If using multiple interactive
3291      * prioritizes an active subsystem, the exec pty, and, lastly, the shell. If using multiple
3311      * Did exec() or read() return because they timed out or because they encountered the end?
3402      * Is the exec pty active?
3999      * Enable request-pty when using exec()
4008      * Disable request-pty when using exec()
4570      * \phpseclib3\Net\SSH2 doesn't properly close most channels.  For exec() channels are normally closed by the server