- 06 Nov, 2017 16 commits
-
-
Nils Goroll authored
vmod_vtc might be a better place for it, but we should probably get $VSC support in vmodtool first and generate the am_boilerplate for it. Ref #2470
-
Nils Goroll authored
-
Nils Goroll authored
Somehow this comment has survived even though we don't use BUILT_SOURCES here any more
-
Nils Goroll authored
I did consider avoiding locks, but as long as the close() in VCA_Shutdown() happens concurrent to vca_acct(), the file descriptor could become invalid at any time, so even if we'd not hit the sock > 0 assertion, other errors could occur / assertions be hit. We could also move the close to vca_acct() and just signal it to finish off, but this would delay the close by the sleep(1), unless we further complicated things with a condvar. Avoiding the lock would require us to make any operation on a socket fd ignore errors, which is totally against our policy to assert on everything. (see vca_tcp_opt_set() for example). So, for the time being, I think simple serialization using a pthread mutex is the safest and simplest solution. A varnish lock would be overkill, as this lock is really only relevant during VCA_Shutdown. IMHO, the primary risk involved here is delayed VCA_Shutdown() due to vca_acct() hanging in a syscall. Famous Last Words - sigh. Fixes #2482
-
Guillaume Quintard authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Geoff Simmons authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 05 Nov, 2017 1 commit
-
-
Nils Goroll authored
Relates to #2480
-
- 04 Nov, 2017 4 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
We were tolerating some unintentional ESI behaviour due to the xml check hitting. We now either avoid running into the xml check or specifically test that we are hitting it. In addition, add some logexpects to tighten checks
-
Nils Goroll authored
ver_p depends on the amount of data we have read ahead, so it is not suitable to get predictable results for ESI testing
-
- 02 Nov, 2017 11 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
for the default symbolname prefix ("vmod_")
-
Poul-Henning Kamp authored
-
Nils Goroll authored
-
- 01 Nov, 2017 2 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 31 Oct, 2017 6 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Dag Haavi Finstad authored
This should help the transition for VMOD writers that rely on the SHA256_* functions.
-
Dridi Boukelmoune authored
Fixes #2468
-
Dag Haavi Finstad authored
-
Poul-Henning Kamp authored
-