Startup failure when running from environment without TERM. #75
Comments
Merged
wdoekes
added a commit
that referenced
this issue
May 14, 2015
Disables the use of ncurses if stdout is not a tty. Observe that that mode disables interactive mode key presses. The status screen is shown, but not if you abort prematurely with ^C. Starting without a proper TERM env now works as long as stdout is not a terminal (closes #75). Also closes #96 without the need for an extra command line option. Thanks @vodik!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you run sipp in foreground mode, it will
screen_init.This fails with the following error if TERM is unset:
I think should retry screen_init with TERM=dummy if it fails. That way you can start a sipp command from a cron job / zabbix job / whatever without having to resort to -bg mode.
(That takes care of this addition https://code.osso.nl/projects/sipp/changeset/48b81a8bd29f/ )
The text was updated successfully, but these errors were encountered: