Stig Sandbeck Mathisen writes:
> Michael Stapelberg writes:
>
>> Yet another alternative might be (and it pains me to say that, but
>> maybe it’s required to not break people’s setups) to have the service
>> file start a wrapper shell script which evaluates
>> /etc/default/varnish before startin
That sounds like a good idea!
On Wed, Mar 1, 2017 at 9:04 PM, Stig Sandbeck Mathisen
wrote:
> Michael Stapelberg writes:
>
> > Yet another alternative might be (and it pains me to say that, but
> > maybe it’s required to not break people’s setups) to have the service
> > file start a wrapper sh
Michael Stapelberg writes:
> Yet another alternative might be (and it pains me to say that, but
> maybe it’s required to not break people’s setups) to have the service
> file start a wrapper shell script which evaluates /etc/default/varnish
> before starting varnish.
That could actually be done
Michael Stapelberg writes:
> Hi,
>
> Gregory Colpart writes:
>> tags 749272 - wontfix
>> severity 749272 serious
>> retitle 749272 varnish doesn't source /etc/default/varnish when started but
>> uses it when reloaded
>
> This bug’s severity now results in varnish and, transitively,
> freeradius
Yet another alternative might be (and it pains me to say that, but maybe
it’s required to not break people’s setups) to have the service file start
a wrapper shell script which evaluates /etc/default/varnish before starting
varnish.
On Wed, Mar 1, 2017 at 7:29 AM, Stig Sandbeck Mathisen
wrote:
>
Hi,
Gregory Colpart writes:
> tags 749272 - wontfix
> severity 749272 serious
> retitle 749272 varnish doesn't source /etc/default/varnish when started but
> uses it when reloaded
This bug’s severity now results in varnish and, transitively, freeradius
being removed from testing, so it warrants
tags 749272 - wontfix
severity 749272 serious
retitle 749272 varnish doesn't source /etc/default/varnish when started but
uses it when reloaded
Hello,
Keeping file /etc/default/varnish when Varnish doesn't source it
is confusing for users. And the worst is that the script
/usr/share/varnish/relo
One more thing about this subject is that actual (jessie)
varnish.service use /usr/share/varnish/reload-vcl as reload script.
But this script seems to use /etc/default/varnish. It may cause strange
behaviour, no ?
> I'll tag this as a "wishlist+wontfix" bug, and keep it open while waiting
> for policy around the use of /etc/default from systemd, upstart, and other
> init systems to settle.
Simulating the sourcing of /etc/default/ by setting
EnvironmentFile to it appears to have become common practice. Searc
On Monday 26 May 2014 09:54:10 Stig Sandbeck Mathisen
wrote:
Hi,
> I'll tag this as a "wishlist+wontfix" bug, and keep it open while
waiting
> for policy around the use of /etc/default from systemd, upstart,
and other
> init systems to settle.
Ack'd.
Thanks!
--
Glennie Vignarajah
http://www.
Control: tag -1 + wontfix
Control: severity -1 wishlist
On Sun, May 25, 2014 at 09:23:01PM +0200, Glennie Vignarajah wrote:
> When varnish is started via systemd, it doesn't use configuration from
> /etc/default/varnish (config section: Alternative 2). In order to use the
> configuration from /et
Package: varnish
Version: 4.0.0-2
Severity: normal
Tags: patch
Hi,
When varnish is started via systemd, it doesn't use configuration from
/etc/default/varnish (config section: Alternative 2).
In order to use the configuration from /etc/default/varnish,
varnish.service should include "EnvironmentFi
12 matches
Mail list logo
