FS#30427 - polipo does not start in backougrnd anymore

Attached to Project: Community Packages
Opened by Michaël Bruneel (mbruneel) - Sunday, 24 June 2012, 20:21 GMT
Last edited by Thorsten Töpper (Atsutane) - Monday, 25 June 2012, 17:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thorsten Töpper (Atsutane)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

After an ugrade to polipo 1.0.4.1-4, the polipo deamon stays in foreground. If polipo is referenced in the DEAMONS list in /etc/rc.conf, the system does not boot properly !
This task depends upon

Closed by  Thorsten Töpper (Atsutane)
Monday, 25 June 2012, 17:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.0.4.1-5 - The file for /etc/conf.d was not installed, thank you.
Comment by Dave Reisner (falconindy) - Sunday, 24 June 2012, 20:29 GMT
Given that there have been no changes to the rc.d script in the last update, I'd say it's more likely that you've broken something else. Did you foolishly run -Syu with --force? I'm guessing that you broke sudo and this has nothing to do with polipo.
Comment by Mr. Smith (eNTi) - Monday, 25 June 2012, 06:34 GMT
the changes introduced with -3 broke the init script for polipo. you can't get out of polipo's listen mode so init is stuck there. i find it highly disturbing, that an init script is capable of doing that. is there a way to change the rc.conf from within grub?
Comment by Jean-Damien Nappey (jdn06) - Monday, 25 June 2012, 08:14 GMT
Similar problem here.
My daemon is not configured to start at boot, but when I try to launch it by a "rc.d start polipo", it fails:
/etc/rc.d/polipo: line 7: /etc/conf.d/polipo.conf: No such file or directory
:: Starting polipo daemon [FAIL]
I tried to copy /etc/polipo/config to /etc/conf.d/polipo.conf but it was not better.
Comment by Michaël Bruneel (mbruneel) - Monday, 25 June 2012, 10:33 GMT
Sorry, the bug was already reported here : https://bugs.archlinux.org/task/30412

@falconindy: No, I have not used --force.

@eNTi: I totally agree, it is highly distrubring. What I did is to boot with an other disk, mount my root partition and edit rc.conf to remove polipo from DEAMONS list.

To fix the problem, we have to create manually /etc/conf.d/polipo.conf and add that line :
POLIPO_ARGS="daemonise=true"

@jdn06 : You should not copy /etc/polipo/config, it is the configuration file for polipo, not for the init script.
Comment by Mr. Smith (eNTi) - Monday, 25 June 2012, 16:01 GMT
so this is it? do you know how much work you just happened to cause to lot of people like me? not only do i have to use WINDOWS to write this on my dual boot machine, i also have to create a boot disk and undo the damage you've caused to my system. the -3 change did NOTHING and yet you managed to made my distro unable to boot. way to go dude, way to go. if you don't know what you are doing, you just shouldn't do it.
Comment by Dave Reisner (falconindy) - Monday, 25 June 2012, 16:03 GMT
Because appending "1" to your kernel cmdline to avoid starting daemons is hard. Tone down the drama a bit and you'll find that life isn't so difficult.
Comment by Jean-Damien Nappey (jdn06) - Monday, 25 June 2012, 17:01 GMT
@ mbruneel The result didn't let me any doubt about it: that was wrong.

I uninstalled and reinstalled the package, but this conf file is still missing, even if Atsutane said it was provided in the package. Easy to correct anyway by creating the missing file: etc/conf.d/polipo.conf, as described by Atsutane

#
# Parameters to be passed to polipo
#
POLIPO_ARGS="daemonise=true"

Loading...