6+ minute apt-daily.service boot delay

[NoOp]

On 11/14/2016 8:53 PM, Tom H wrote:
> It's better to use a dropin:
> 
> # mkdir -p /etc/systemd/system/miredo.service.d
> # echo "[Unit]" > /etc/systemd/system/miredo.service.d/network-online.conf
> # echo "After=network-online.target" >>
> /etc/systemd/system/miredo.service.d/network-online.conf
> # echo "Wants=network-online.target" >>
> /etc/systemd/system/miredo.service.d/network-online.conf
> # systemctl daemon-reload
> 
> otherwise your changes to "/lib/systemd/system/miredo.service" will be
> over-written by the next update to the package that owns it.

I purged miredo & applied your suggestions - works:

/etc/init.d/miredo status
● miredo.service - Teredo IPv6 tunneling
   Loaded: loaded (/lib/systemd/system/miredo.service; enabled; vendor
preset: enabled)
  Drop-In: /etc/systemd/system/miredo.service.d
           └─network-online.conf
   Active: active (running) since Tue 2016-11-15 11:36:06 PST; 1min 49s ago
  Process: 2296 ExecStartPre=/usr/sbin/miredo-checkconf -f
/etc/miredo/miredo.conf (code=exited, status=0/SUCCESS)
 Main PID: 2385 (miredo)
   CGroup: /system.slice/miredo.service
           ├─2385 /usr/sbin/miredo -f
           ├─2395 /usr/sbin/miredo -f
           └─2398 /usr/lib/x86_64-linux-gnu/miredo/miredo-privproc 3

Nov 15 11:36:06 gg systemd[1]: Starting Teredo IPv6 tunneling...
Nov 15 11:36:06 gg systemd[1]: Started Teredo IPv6 tunneling.
Nov 15 11:36:07 gg miredo[2385]: miredo[2385]: Starting...
Nov 15 11:36:07 gg miredo[2385]: Starting...
Nov 15 11:36:07 gg miredo[2385]: miredo[2395]: New Teredo address/MTU
Nov 15 11:36:07 gg miredo[2385]: miredo[2395]: Teredo pseudo-tunnel started
Nov 15 11:36:07 gg miredo[2385]: miredo[2395]:  (address:
2001:0:53aa:64c:1...0)
Nov 15 11:36:07 gg miredo[2395]: New Teredo address/MTU
Nov 15 11:36:07 gg miredo[2395]: Teredo pseudo-tunnel started
Nov 15 11:36:07 gg miredo[2395]:  (address:
2001:0:53aa:64c:10fb:3bad:e7f9:...0)

Thanks again Tom!