1. 19 Nov, 2012 5 commits
    • Poul-Henning Kamp's avatar
      Reenable CLANG · b5700628
      Poul-Henning Kamp authored
      b5700628
    • Tollef Fog Heen's avatar
      Only use readline/history.h if no edit/readline/redline.h · 70bce6bf
      Tollef Fog Heen authored
      it seems edit/readline/readline.h and readline/history.h are
      incompatible on FreeBSD, so only include one.  Hopefully this works on
      OpenBSD still.
      70bce6bf
    • Tollef Fog Heen's avatar
      Add vtree.h to _SOURCES · 2038df57
      Tollef Fog Heen authored
      2038df57
    • Federico G. Schwindt's avatar
      PATCH: fix some warnings during configure/compilation · ae52a414
      Federico G. Schwindt authored
      Hi,
      
      The diff below fixes one warning during configure and two during compilation on OpenBSD (and maybe elsewhere):
      
      checking pthread_np.h usability... no
      checking pthread_np.h presence... yes
      configure: WARNING: pthread_np.h: present but cannot be compiled
      configure: WARNING: pthread_np.h:     check for missing prerequisite headers?
      configure: WARNING: pthread_np.h: see the Autoconf documentation
      configure: WARNING: pthread_np.h:     section "Present But Cannot Be Compiled"
      configure: WARNING: pthread_np.h: proceeding with the compiler's result
      configure: WARNING:     ## -------------------------------------------- ##
      configure: WARNING:     ## Report this to varnish-dev@varnish-cache.org ##
      configure: WARNING:     ## -------------------------------------------- ##
      
      varnishadm.c:190: warning: implicit declaration of function 'add_history'
      
      cache/cache_main.c:82: warning: implicit declaration of function 'pthread_set_name_np'
      
      Comments? OK?
      
      f.-
      ae52a414
    • Tollef Fog Heen's avatar
      Minor cleanups in varnishtop · 89bf18a8
      Tollef Fog Heen authored
      Some minor cleanups, no functional changes.  Thanks to Federico
      Schwindt for pointing this out.
      89bf18a8
  2. 16 Nov, 2012 1 commit
    • Lasse Karstensen's avatar
      Clarify which timeout was reached · fc7732d2
      Lasse Karstensen authored
      When looking at varnishlog it looks like it is send_timeout that was reached,
      but in fact it is idle_send_timeout. Clarify the language so the user
      understands which parameter to adjust.
      fc7732d2
  3. 13 Nov, 2012 3 commits
  4. 12 Nov, 2012 4 commits
  5. 07 Nov, 2012 1 commit
  6. 05 Nov, 2012 3 commits
  7. 31 Oct, 2012 2 commits
  8. 29 Oct, 2012 5 commits
  9. 25 Oct, 2012 8 commits
  10. 24 Oct, 2012 8 commits