git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@675 d4fa192b-c00b-0410-8231-f00ffab90ce4

CLI sources yell at the same time.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@674 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@673 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@672 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@671 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@670 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@669 d4fa192b-c00b-0410-8231-f00ffab90ce4

for ever.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@668 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@667 d4fa192b-c00b-0410-8231-f00ffab90ce4

remove two unused variables.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@666 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fix function arg type


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@665 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@664 d4fa192b-c00b-0410-8231-f00ffab90ce4

free buffer on error.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@663 d4fa192b-c00b-0410-8231-f00ffab90ce4

Remove unused #include


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@662 d4fa192b-c00b-0410-8231-f00ffab90ce4

Make VCL_Load static, and give it a NULL check.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@661 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@660 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@659 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@658 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@657 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@656 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@655 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@654 d4fa192b-c00b-0410-8231-f00ffab90ce4

developer compatible.

POSIX, no surprise, doesn't really tell what should happen to a threaded
process which forks and consequently implemenations vary somewhat,
from Solaris which seems to Do The Right Thing, via Linux where it
works "most of the time" and to FreeBSD which more or less actively
sabotages any such attempt.

Grin and live with it...



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@653 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@652 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@651 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@650 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@649 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@648 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@647 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@646 d4fa192b-c00b-0410-8231-f00ffab90ce4

It's general enough to find other uses, but right now it's only for
the manager process.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@645 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@644 d4fa192b-c00b-0410-8231-f00ffab90ce4

spurious first entries.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@643 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@642 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@641 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@640 d4fa192b-c00b-0410-8231-f00ffab90ce4

as well allow their manipulation also when the child is not
running.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@639 d4fa192b-c00b-0410-8231-f00ffab90ce4

Keep track of all loaded VCL programs in the manager and tell the
child to load them via VCL.

Don't start he acceptor thread until a "start" command cones down
the CLI.

XXX: Right now we leak stuff when a VCL program is dicarded



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@638 d4fa192b-c00b-0410-8231-f00ffab90ce4

Take default_vcl out of heritage.

Keep track of all compiled VCL files and delete them at
exit.

After starting child, use CLI to load all vcl programs
and then issue "start" via the CLI.

In the cacher, don't start the acceptor until we get
a start command.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@637 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@636 d4fa192b-c00b-0410-8231-f00ffab90ce4