<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 9, 2016, at 7:23 PM, Oliver Jowett <<a href="mailto:oliver@mutability.co.uk" class="">oliver@mutability.co.uk</a>> wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class=""></blockquote><div class="">init.d scripts are usually conffiles so only get removed on purge, not on simple package removal. Traditionally the first thing they do is test that the corresponding binary is actually </div></div></div></div></div></blockquote><div><br class=""></div><div>Really? Init.d scripts are configured files and not part of the “package? That’s surprising to me, and doesn’t seem quite right.</div><div><br class=""></div><div>Eric’s How To has the purge option (<span style="color: rgb(69, 69, 69); font-family: Menlo;" class="">apt-get -y remove --purge ntp</span>). So this should take care of the init.d scripts. Is there anything else that should be added to make sure all remnants of the Debian NTP is gone?</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">"update-rc.d foo disable" or "systemctl mask foo" are probably the canonical ways to disable the package scripts.</div></div></div></div></blockquote><br class=""></div><div>Would these work or be needed if “purge” was used?</div><div><br class=""></div><div>Thanks,</div><div>Frank</div><br class=""></body></html>