intrigeri writes:
> I'll let you handle that: I merely worked on this bug to give a hand
> and help a bit polish Jessie (and more specifically, the transition to
> systemd), but I don't suffer from it myself... so far.
I solved my "transition" to systemd with `apt-get purge systemd` ;-)
> Assuming that nobody proposes the changes I've suggested upstream,
> or that upstream rejects it (which I would fully understand), then
> I see two ways out:
>
> a) Drop the EnvironmentFile= support, on the grounds that it's
> incomplete and misleading. Then document in README.Debian that
> under systemd:
> - /etc/default/docker is ignored (and maybe make that file point
> to README.Debian);
> - one can customize the daemon startup options and runtime
> environment via the standard systemd drop-in override mechanism.
>
> b) Make it clear, in /etc/default/docker, which options take effect
> when running under systemd, and which ones don't. And add a note
> about the Environment= directive that allows to set the latter
> (http_proxy, TMPDIR); this note could live in /etc/default/docker
> and/or in README.Debian.
>
> Plan (b) seems quite acceptable, and perhaps easier to implement.
> Plan (a) feels cleaner, more consistent, and easier to grasp by the
> user IMO.
I initially suggested b) and still think that is the best way to go
about it. Documentation in that file could even mention both ways to
get things to work under systemd: remove the `export` or configure in
places where systemd looks. I prefer /etc/default/, where quite a
number of other system components also put their defaults for the
sysadmin to tweak.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
