<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 14, 2016 at 8:34 AM, Reindl Harald <span dir="ltr"><<a href="mailto:h.reindl@thelounge.net" target="_blank">h.reindl@thelounge.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>Am 14.08.2016 um 14:29 schrieb Tom Browder:<br></span></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3. If Debian 8 is running systemd for a service, why do I need an<br>
entry for a service in init.d?<br>
</blockquote>
<br></span>
you don't</blockquote><div><br></div><div>If I'm not mistaken, systemd is still referenced in /etc/init.d in Debian in some way, because systemd is still de facto transitional: and thus continues to maintain backward compatibility with SysVinit. So many people will probably not understand why systemd continues to be linked to various parts of the old SysVinit system -- when it is supposed to be outright replacing it.</div><div><br></div><div>Point is: it takes time to properly and safely transition core infrastructure.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div></div></div>