Menu
▾
▴
[privoxy-devel] [ ijbswa-Bugs-1386919 ] OpenSuSE10 and Privoxy 3.0.3: rcprivoxy script fails
|
From: SourceForge.net <no...@so...> - 2006-09-28 06:45:31
|
Bugs item #1386919, was opened at 2005-12-21 09:36 Message generated for change (Comment added) made by vorkoster You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1386919&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: suse-specific Group: version 3.3 >Status: Open Resolution: None Priority: 5 Submitted By: vorkoster (vorkoster) Assigned to: Stefan Waldherr (swa) Summary: OpenSuSE10 and Privoxy 3.0.3: rcprivoxy script fails Initial Comment: Hi, under OpenSuSE 10 using Privoxy 3.0.3 (SuSE-included) the following problems occur: 1.: The provided config file has wrong paths and needs to be edited manually: - confdir /var/lib/privoxy/etc - logdir /var/lib/privoxy/log 2.: It's not possible to run rcprivoxy ("failed"). Workaround: starting Privoxy by "/usr/sbin/privoxy /var/lib/privoxy/etc/config" This way privoxy works as usual. Maybe someone could provide a new rcprivoxy script or point me to the needed corrections? I would like to use privoxy as a "service" in the usual way, so the rcprivoxy script would be much better :) Cheers, -Michael ---------------------------------------------------------------------- >Comment By: vorkoster (vorkoster) Date: 2006-09-28 06:45 Message: Logged In: YES user_id=1083417 Please don't remove SuSE support. Privoxy has been successfully running on my SuSE boxes for years now :) ---------------------------------------------------------------------- Comment By: Hal Burgiss (hal9) Date: 2006-09-28 02:08 Message: Logged In: YES user_id=322640 There is nobody now that can test and implement such changes for SuSE. Sorry. Nobody on the team uses SuSE. If someone wants to volunteer that would solve the entire issue. If not, we will be removing SuSE specific support soon, so as not to confuse people. ---------------------------------------------------------------------- Comment By: cyberquiet (cyberquiet) Date: 2006-04-23 13:55 Message: Logged In: YES user_id=1404243 Thank you very much! Now I can finally enjoy privoxy on my SUSE box! Anyway, what are the developers waiting to fix this problem? ---------------------------------------------------------------------- Comment By: vorkoster (vorkoster) Date: 2005-12-23 07:01 Message: Logged In: YES user_id=1083417 Hello again, seems that I am dancing with myself here :) Here my final summarization of my experiences with Privoxy on OpenSuSE 10: a) installation of downloadable version fails (see comment above) b) installation of SuSE-provided version is possible, but needs some work: - exchange script in /etc/init.d/privoxy by the one above or the other attached one - check existing user and group named privoxy - chown/chgrp user/group "privoxy" for /var/lib/privoxy and subdirs (standard root) - check config file for confdir and logdir (see above) I still think it's worth the little effort. For me, Privoxy has been working flawlessly for years now! Happy privoxing :) Cheers, -Michael ################################################ #! /bin/sh # ******************************************************************** # # File : $Source: /cvsroot/ijbswa/current/privoxy.init.suse,v $ # # Purpose : This shell script takes care of starting and stopping # privoxy. # # Copyright : Written by and Copyright (C) 2001 the SourceForge # Privoxy team. http://www.privoxy.org/ # # Based on the Internet Junkbuster originally written # by and Copyright (C) 1997 Anonymous Coders and # Junkbusters Corporation. http://www.junkbusters.com # # This program is free software; you can redistribute it # and/or modify it under the terms of the GNU General # Public License as published by the Free Software # Foundation; either version 2 of the License, or (at # your option) any later version. # # This program is distributed in the hope that it will # be useful, but WITHOUT ANY WARRANTY; without even the # implied warranty of MERCHANTABILITY or FITNESS FOR A # PARTICULAR PURPOSE. See the GNU General Public # License for more details. # # The GNU General Public License should be included with # this file. If not, you can view it at # http://www.gnu.org/copyleft/gpl.html # or write to the Free Software Foundation, Inc., 59 # Temple Place - Suite 330, Boston, MA 02111-1307, USA. # # Revisions : # $Log: privoxy.init.suse,v $ # Revision 1.3.2.1 2003/03/17 14:04:16 oes # No longer use obsolete rc.config # # Revision 1.3 2002/03/26 22:29:55 swa # we have a new homepage! # # Revision 1.2 2002/03/24 11:40:14 swa # name change # # Revision 1.1 2002/03/24 11:23:44 swa # name change # # Revision 1.7 2002/03/11 11:44:46 oes # Working in suggestions by Thorsten Kukuk <ku...@su...> # # Revision 1.6 2002/03/09 14:56:34 swa # wrong user.group # # Revision 1.5 2002/03/08 21:39:59 oes # setgid to nogroup # # Revision 1.4 2002/03/05 19:54:37 oes # Preliminary version of SuSE 8.0-certified init script ,-) # # Revision 1.3 2002/03/05 05:28:05 oes # Added pidfile creation # # Revision 1.2 2001/09/10 16:25:46 swa # jb did not start. none of the arguments worked. fixed. # # Revision 1.1 2001/06/08 20:53:36 swa # use buildroot, export init to separate file (better manageability) # # # # ********************************************************************/ ### BEGIN INIT INFO # Provides: privoxy # Required-Start: $network $syslog $remote_fs # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Starts Privoxy ### END INIT INFO . /etc/rc.status rc_reset case "$1" in start) echo -n "Starting Privoxy" if [ ! -f /var/run/privoxy.pid ] || ! kill -0 `cat /var/run/privoxy.pid` 2> /dev/null; then /usr/sbin/privoxy --user privoxy.privoxy --pidfile /var/run/privoxy.pid /etc/privoxy/config 2> /dev/null else false fi rc_status -v ;; stop) echo -n "Shutting down Privoxy" killproc -TERM /usr/sbin/privoxy && rm -f /var/run/privoxy.pid rc_status -v ;; reload) echo -n "Reloading Privoxy" kill -HUP `cat /var/run/privoxy.pid` rc_status -v ;; try-restart) $0 stop && $0 start rc_status ;; restart) $0 stop $0 start rc_status ;; status) echo -n "Checking for Privoxy" checkproc /usr/sbin/privoxy rc_status -v ;; *) echo "Usage: $0 {start|restart|reload|status|stop}" exit 1 esac rc_exit ################################################################ ---------------------------------------------------------------------- Comment By: vorkoster (vorkoster) Date: 2005-12-22 10:13 Message: Logged In: YES user_id=1083417 Hello again, after a bit more testing, the problem could be the "chroot" option in rcprivoxy script. The following workaround script seems to do the essential things at least (starting/stopping privoxy): ###################### start script ################### #!/bin/sh ### BEGIN INIT INFO # Provides: rcprivoxy-workaround # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 5 # Description: "/usr/sbin/rcprivoxy" workaround 22.12.2005 vorkoster OpenSuSE10 ### END INIT INFO case "$1" in 'start') /usr/sbin/privoxy /var/lib/privoxy/etc/config --user privoxy.privoxy --pidfile /var/run/privoxy.pid ;; 'stop') ps -ef | grep privoxy | grep -v grep | cut -c 10-15 | xargs kill -9 ;; *) echo "Usage: $0 { start | stop }" ;; esac exit 0 ####################### end script ######################## Maybe that can assist the developers in making a "real" correction for the SuSE version. HTH, -Michael ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1386919&group_id=11118 |