On Sat, Nov 4, 2017 at 6:57 AM, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: > privoxy.service most certainly has: > > Wants=network-online.target > After=network-online.target ... > However, privoxy just failed to start for me, after a reboot. I was curious about this, so I went back to the beginning. I take back what I said earlier. This should work on a default Fedora system without any additional steps. I tested this on my own Fedora laptop, where the NetworkManager-wait-online service is in its default state, and the network link is provided by WiFi. I installed privoxy and configured it to listen on the IP address that would be assigned by DHCP, and rebooted the system. On boot, the service started after the network came online, just like you would expect (or, just like you should be able to expect, ideally). I did some additional testing by creating a shell script, /usr/local/bin/ip-log, that runs "/usr/sbin/ip addr show | logger" and then executed it during startup by running "systemctl edit NetworkManager-wait-online". In the override file, I added two lines: [Service] ExecStart=/usr/local/bin/ip-log ... and rebooted. Boot records that most services start 14-16 seconds past the minute and that NetworkManager starts setting up. It takes six seconds to connect to WiFi and get an address from DHCP. At 22 seconds past the minute, the output of "ip addr show" is logged, and then privoxy starts. So I'm not actually certain why this doesn't work on your system, and I'm interested in what comes of that bug. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
