1. 21 Nov, 2016 2 commits
  2. 20 Nov, 2016 1 commit
  3. 18 Nov, 2016 15 commits
  4. 17 Nov, 2016 1 commit
    • Poul-Henning Kamp's avatar
      Don't use SIGHUP, it fails if varnishtest is run under nohup(1) · feac0301
      Poul-Henning Kamp authored
      We recognize only the most famous signals by name SIGTERM, SIGINT
      and SIGKILL, if you want a special signal you will have to use "-15"
      or whatever.
      
      The primary reason for this is that there is still no portable API
      for translating "SIGXXX" to an integer.
      
      It used to be that bin/kill.c contained an array:
      
      	const char *const sys_signame[NSIG] = {
      		[0] =           "Signal 0",
      		[SIGHUP] =      "HUP",
      		[SIGINT] =      "INT",
      		[SIGQUIT] =     "QUIT",
      		[SIGILL] =      "ILL",
      		[...]
      
      BSD unix sensibly moved this into libc, to avoid duplicating
      this all over the place, but Linux has not done that.
      
      The right way to do this, would have been to have <signal.h>
      contain a table:
      
      	#ifdef SIGNAL_DOC(n,s,l)
      	SIGNAL_DOC(1, "HUP", "Hangup")
      	SIGNAL_DOC(2, "INT", "Interrupt")
      	...
      	#endif
      
      That way nobody would ever need another #ifdef SIGFOO.
      
      Anyway...
      
      Rather than pointlessly add a semi-complete list of signals no
      sensible person should ever use in a varnishtest (SIGWINCH anybody
      ?) we support the famous three by name, and the rest by number.
      feac0301
  5. 16 Nov, 2016 1 commit
  6. 15 Nov, 2016 2 commits
  7. 14 Nov, 2016 5 commits
  8. 11 Nov, 2016 2 commits
  9. 09 Nov, 2016 6 commits
  10. 08 Nov, 2016 4 commits
  11. 07 Nov, 2016 1 commit