• Nils Goroll's avatar
    fix signal handling in varnishtop and varnishhist · 47579871
    Nils Goroll authored
    Using vut->last_sighup was not adequate, because the VUT_Main loop might
    have terminated for some other signal or because of EOF.
    
    On the other hand, we do not want to end the curses loop just because
    the VUT_Main loop has ended in order to continue to display the last
    state (and maybe the EOF in the top right corner).
    
    So while I see that checking just one flag has some beauty to it, I do
    think that directly checking the signal counters is both simple and
    robust.
    
    Fixes #3088 for varnishtop and varnishhist
    47579871
Name
Last commit
Last update
.circleci Loading commit data...
.github Loading commit data...
bin Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
tools Loading commit data...
.dir-locals.el Loading commit data...
.envrc Loading commit data...
.gitignore Loading commit data...
.lgtm.yml Loading commit data...
.syntastic_c_config Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.Packaging Loading commit data...
README.rst Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish-legacy.m4 Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...