I added it to the start up program list, you can see it try to start it during boot if you hit the ESC key, but it says failed. I did Tor the same way and that one works. Permissions problem? Once the system is up and running, I have to go into terminal as root user and then enter privoxy. Then it works.
Thanks
On Tue, 20 Dec 2011 22:36:03 +0000, Doug08 wrote:
> I added it to the start up program list, you can see it try to start it
> during boot if you hit the ESC key, but it says failed. I did Tor the
> same way and that one works. Permissions problem? Once the system is up
> and running, I have to go into terminal as root user and then enter
> privoxy. Then it works.
>
> Thanks
It would be helpful for you to indicate what version of openSUSE you’re
using and what steps you took to add it to the startup program list. (ie,
system-wide or when you login - for example - and if the latter, which
desktop you’re using would be very helpful as well). 
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Your right, not enough info. Sorry. I did it a long time ago, just tired of having to start it in terminal. I’m pretty sure I edited a start up file with kwrite.
Dell Vostro 1500
Linux 2.6.34.10-0.4-desktop i686
Current user: doug@linux-rvej.site
System: openSUSE 11.3 (i586)
KDE: 4.4.4 (KDE 4.4.4) “release 3”
On Wed, 21 Dec 2011 03:06:02 +0000, Doug08 wrote:
> Your right, not enough info. Sorry. I did it a long time ago, just tired
> of having to start it in terminal. I’m pretty sure I edited a start up
> file with kwrite.
>
> Dell Vostro 1500
>
> Linux 2.6.34.10-0.4-desktop i686 Current user: doug@linux-rvej.site
> System: openSUSE 11.3 (i586)
> KDE: 4.4.4 (KDE 4.4.4) “release 3”
So was this a system startup that you’re trying to use, or a login
startup?
If it’s a system startup, what is in your init script? (be sure to post
it in code tags so the formatting isn’t lost)
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
System start up.
Here is the /etc/rc.d/privoxyd file:
#! /bin/sh
. /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
# set up chroot dir
for i in /etc/{resolv.conf,host.conf,hosts,localtime}; do
cp -p $i /var/lib/privoxy/etc/ &>/dev/null
|| { echo “…$0:$LINENO: could not copy $i to chroot jail”; rc_failed; rc_status -v1; exit 6; }
done
libdir=/$(basename $(echo /var/lib/privoxy/lib*))
for i in /$libdir/{libresolv.so.2,libnss_dns{,6}.so.2}; do
if -s $i ]; then
cp -p $i /var/lib/privoxy/$libdir/
|| { echo “…$0:$LINENO: could not copy $i to chroot jail”; rc_failed; rc_status -v1; exit 6; }
fi
done
# started process in privoxy wait 1 sec and then check forked process (e.g child died due to missing config files),
# so we need a time (-T 1 option) while forked process checks config file
# better options for startproc could be -w, but this options is available only since 11.2
startproc -T 1 /usr/sbin/privoxy --user privoxy.privoxy --pidfile /var/run/privoxy.pid --chroot /etc/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
# remove libraries from the chroot jail, just so they are not left over
# if the server is deinstalled
rm -f /var/lib/privoxy/lib*/*
rc_status -v
;;
reload)
echo -n "Reloading Privoxy"
kill -HUP `cat /var/run/privoxy.pid`
rc_status -v
;;
try-restart)
$0 status >/dev/null && $0 restart
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
On Thu, 22 Dec 2011 00:06:03 +0000, Doug08 wrote:
> System start up.
>
> Here is the /etc/rc.d/privoxyd file:
At a glance that looks OK to me.
What runlevels do you have it enabled for (in the YaST runlevel editor -
switch to ‘expert’ mode).
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Runlevel show “Yes” with an asterisk next to it in simple mode, but in expert mode it says “No” with run levels 3 & 5. How can it show yes and no? Obviously the expert mode is telling me the truth, not the simple mode.
Thanks
On Thu, 22 Dec 2011 15:06:02 +0000, Doug08 wrote:
> Runlevel show “Yes” with an asterisk next to it in simple mode, but in
> expert mode it says “No” with run levels 3 & 5. How can it show yes and
> no? Obviously the expert mode is telling me the truth, not the simple
> mode.
Hmmm, that’s odd, certainly.
I’m thinking that perhaps the network service isn’t started up when it
gets to that point, though the dependencies seem to be set up properly.
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
This happened after I did an upgrade from Suse 11.1 to 11.3. It always worked before the upgrade. Must be some file I can edit that will allow privoxy to activate as root before the desktop screen shows up.
Thanks
I have tor.desktop in the .kde4/Autostart folder to run once the desktop logs on. It works just fine. Tor is located in /usr/bin which is root root 755. I added privoxy.desktop(which is also root root 755) to the autostart folder with tor…I get confirmation that both commands have been executed. I checked to see if Privoxy is running, and it is not. I have to go into terminal as SU, then it runs. Both programs are root programs. One runs, one does not. Weird. I think it is a privoxy file issue.
On Fri, 23 Dec 2011 03:26:02 +0000, Doug08 wrote:
> I have tor.desktop in the .kde4/Autostart folder to run once the desktop
> logs on. It works just fine. Tor is located in /usr/bin which is root
> root 755. I added privoxy.desktop(which is also root root 755) to the
> autostart folder with tor…I get confirmation that both commands have
> been executed. I checked to see if Privoxy is running, and it is not. I
> have to go into terminal as SU, then it runs. Both programs are root
> programs. One runs, one does not. Weird. I think it is a privoxy file
> issue.
Are you using NetworkManager to manage your network? If you are, it
typically won’t have the network fully started until you’ve logged into
the desktop.
You might try switching to the ‘traditional ifup’ method and see if that
fixes the issue.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C