Re: Polipo at system startup

> That's an init script. I'm going to assume you have polipo installed
> from the fedora repositories. The traditional way of enabling an init
> script on boot is '/sbin/chkconfig --level 35 polipo on'.

Please note that Polipo was originally designed to be started by
daemontools or runit; support for traditional double-fork daemonisation
was only added grudgingly, almost as an afterthought.  (That's why you
need -D in order to get Polipo to daemonise.)

I'm glad that Fedora has finally given up on the heap of mis-designed
garbage that is SV init[1].  If so, I would suggest that the Fedora RPM of
Polipo should be reworked to start Polipo runit-style, as intented.

(Note that Polipo does not, and will not, support systemd-style soscket-
activated activation.  Thankfully, systemd is designed to also support
runit-style daemons.)

-- Juliusz

[1] I'm refraining from an extended rant on the utter stupidity of
    System V Init.

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2