varnishctl?

[Tollef Fog Heen]

]] Dridi Boukelmoune

> On Tue, Jan 28, 2014 at 8:07 AM, Tollef Fog Heen
> <tfheen at varnish-software.com> wrote:
> > ]] Dridi Boukelmoune
> >
> > > I find the idea compelling, but I've had issues with apachectl.
> >
> > Your problems seem to be "apachectl has bugs", and I wrote "something
> > like apachectl", meaning that we'll implement a different set of bugs.
> > :-)
> 
> As long as the bugs are well documented ;-)

We'll do our best.

> >> I really like the idea of a varnishctl that could be used downstream
> >> to build services on top of systemd, upstart etc. But I'd go for a
> >> simple pass-through command with simple sub-commands such as
> >> start/stop/restart/reload/configtest that would just add sugar such as
> >> "configtest on restart" and nothing more.
> >
> > In the stack, I'd want to have the init scripts call varnishctl, not the
> > other way around.
> 
> Sorry, this is what I meant. SysVinit, systemd, upstart and the like
> that would use varnishctl. By downstream I mean distributions since
> they mean you as an upstream of their varnish packages.

Ah, right, then we're in agreement where it would fit.

> >> > Suggestion 2:
> >> >
> >> > Extend varnishadm to not only be able to talk to varnishd, but also
> >> > start and stop the management process, do a config test and so on.
> >>
> >> Would that mean 3 processes in varnishd ?
> >
> > No, that wasn't my intention.  What would the third one be?
> 
> I don't know ; if varnishd has only two processes as it currently has,
> how would you stop the management process ? I understand the feature
> to be similar to the current stop/start of the child process through
> varnishadm.

In this case, varnishadm would send a sigint to varnishd (the management
process) or tell it to exit through the CLI and then wait for it to exit
before returning.

-- 
Tollef Fog Heen
Technical lead | Varnish Software AS
📞: +47 21 98 92 64
We Make Websites Fly!