- 26 Nov, 2016 4 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
They live as private macros in varnish.m4, which is now included in the Varnish build during the autogen phase. This way it is now possible to dogfood on macros we distribute downstream. Considering how simple they are, they could be made public macros for the convenience of VMOD or VUT writers. We don't need to have the LIBS-saving-dance in configure.ac for every single dependency.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 25 Nov, 2016 6 commits
-
-
Poul-Henning Kamp authored
There is now similar logic in varnishd, but by then it may be too late already, but that still improves chances for the users.
-
Poul-Henning Kamp authored
We don't need AC_PROG_CPP, because we don't use the C preprocessor standalone for anything. It's not obvious that anybody needs AC_PROG_MAKE_SET ever, it looks like a band-aid for some crappy Win98-related tinker-toy-compiler. Amazing (or not...) that nobody in the autocrap community ever got the idea to add "What made AC_FOOBAR necessary" explanations to their documentation or changelogs.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
This should stabilize r00962 on Ubuntu and make -spersistent less useless on same.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 24 Nov, 2016 2 commits
-
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
- 22 Nov, 2016 1 commit
-
-
Dridi Boukelmoune authored
Should the minimum be bumped from 9k to 12k?
-
- 21 Nov, 2016 5 commits
-
-
Poul-Henning Kamp authored
This goes into the 'id' on the server side, and is necessary because certain distingushing facts, like compiler/target architecture, cannot be determined until after autogen and the configure it creates have been run.
-
Nils Goroll authored
This should make distcheck happy on SmartOS
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
-
- 20 Nov, 2016 1 commit
-
-
Poul-Henning Kamp authored
-
- 18 Nov, 2016 15 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Don't request a TTY
-
Nils Goroll authored
The hardcoded paths are the one thing which has kept me from sing autogen.des regularly
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
CI setup.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Use SIGKILL which is sure to work.
-
Poul-Henning Kamp authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
- 17 Nov, 2016 1 commit
-
-
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.
-
- 16 Nov, 2016 1 commit
-
-
Poul-Henning Kamp authored
-
- 15 Nov, 2016 2 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 14 Nov, 2016 2 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
For epoll, we tolerate spurious reports, for all other waiters we assert. fixes #2117
-