Re: Starting privoxy at startup
I've solved this, after a fashion. Thanks again for your help. It turns out that the logfile directory, /var/log/privoxy, was accessible by root only, even with permissions changed. (Is this a basic BSD security thing? I googled that a little but was not sure.) I guessed it has been done for a reason and did not try to break it. So, I changed the location for logfile to /usr/local/etc/privoxy/log, copied the files from /var/log/privoxy there, changed their permissions, and put a little shell script in ~./.kde/Autostart to start privoxy and to point to the config file. My guess is that user privoxy could not get into /var/log/privoxy either, and that with the logfile directory changed and with all the flags (user=privoxy, /usr/local/etc/privoxy/conf) set in rc.conf, it would have worked as well. I don't know how to set two flags at once (my guess is a line saying privoxy_flags=user privoxy, /usr/local/etc/privoxy/config but I am not sure of the format and couldn't find documentation. Thanks, Oliver On Friday 31 March 2006 11:43, you wrote: Oliver Iberien wrote: Sorry to drag this out, but I still have not got this to work. I've looked at the permissions of the files involved but nothing untoward shows up. I think. There is just the conf file and the stuff in /var/log, right? How should their permissions look? Configuration files go in /usr/local/etc/privoxy/ not /var/log. If I wanted to have two flags for privoxy in rc.conf -- the one below and one pointing to /usr/local/etc/privoxy/conf -- what would that look like? Sorry, no idea. I'm not privoxy expert, just a user. I can show you what I have working, but that's about it. Here's a listing of the configuration files in my installation. Most if not all of these were installed by the port. If you don't have them, I would reinstall the port. $ls -AlR /usr/local/etc/privoxy/ -rw-r--r-- 1 root wheel781 Oct 18 00:55 blocklist.action -rw-r--r-- 1 root wheel 1080 Nov 14 12:22 config -rw-r--r-- 1 root wheel 31297 Nov 16 04:53 config.original -r--r--r-- 1 root wheel 39617 Feb 10 06:28 default.action -r--r--r-- 1 root wheel 28943 Feb 10 06:28 default.filter -rw-r--r-- 1 root wheel 0 Jul 29 2005 mod-support-and-service drwxr-xr-x 2 root wheel 1024 Feb 10 06:28 templates/ -r--r--r-- 1 root wheel 3366 Feb 10 06:28 trust ./templates: -r--r--r-- 1 root wheel 9468 Feb 10 06:28 blocked -r--r--r-- 1 root wheel 4615 Feb 10 06:28 cgi-error-404 -r--r--r-- 1 root wheel 4930 Feb 10 06:28 cgi-error-bad-param -r--r--r-- 1 root wheel 4201 Feb 10 06:28 cgi-error-disabled -r--r--r-- 1 root wheel 3877 Feb 10 06:28 cgi-error-file -r--r--r-- 1 root wheel 4347 Feb 10 06:28 cgi-error-file-read-only -r--r--r-- 1 root wheel 5012 Feb 10 06:28 cgi-error-modified -r--r--r-- 1 root wheel 4965 Feb 10 06:28 cgi-error-parse -r--r--r-- 1 root wheel 4839 Feb 10 06:28 cgi-style.css -r--r--r-- 1 root wheel 4640 Feb 10 06:28 connect-failed -r--r--r-- 1 root wheel 3769 Feb 10 06:28 default -r--r--r-- 1 root wheel 6107 Feb 10 06:28 edit-actions-add-url-form -r--r--r-- 1 root wheel 37799 Feb 10 06:28 edit-actions-for-url -r--r--r-- 1 root wheel602 Feb 10 06:28 edit-actions-for-url-filter -r--r--r-- 1 root wheel 12888 Feb 10 06:28 edit-actions-list -r--r--r-- 1 root wheel 2230 Feb 10 06:28 edit-actions-list-button -r--r--r-- 1 root wheel 5086 Feb 10 06:28 edit-actions-list-section -r--r--r-- 1 root wheel 3583 Feb 10 06:28 edit-actions-list-url -r--r--r-- 1 root wheel 5863 Feb 10 06:28 edit-actions-remove-url-form -r--r--r-- 1 root wheel 6199 Feb 10 06:28 edit-actions-url-form -r--r--r-- 1 root wheel523 Feb 10 06:28 mod-local-help -r--r--r-- 1 root wheel 1243 Feb 10 06:28 mod-support-and-service -r--r--r-- 1 root wheel296 Feb 10 06:28 mod-title -r--r--r-- 1 root wheel325 Feb 10 06:28 mod-unstable-warning -r--r--r-- 1 root wheel 4730 Feb 10 06:28 no-such-domain -r--r--r-- 1 root wheel 4452 Feb 10 06:28 show-request -r--r--r-- 1 root wheel 12471 Feb 10 06:28 show-status -r--r--r-- 1 root wheel 4180 Feb 10 06:28 show-status-file -r--r--r-- 1 root wheel 5316 Feb 10 06:28 show-url-info -r--r--r-- 1 root wheel 4859 Feb 10 06:28 show-version -r--r--r-- 1 root wheel 7153 Feb 10 06:28 toggle -r--r--r-- 1 root wheel 3489 Feb 10 06:28 toggle-mini -r--r--r-- 1 root wheel 5728 Feb 10 06:28 untrusted Regards, Pete ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Starting privoxy at startup
Sorry to drag this out, but I still have not got this to work. I've looked at the permissions of the files involved but nothing untoward shows up. I think. There is just the conf file and the stuff in /var/log, right? How should their permissions look? If I wanted to have two flags for privoxy in rc.conf -- the one below and one pointing to /usr/local/etc/privoxy/conf -- what would that look like? Thanks, Oliver On Monday 27 March 2006 10:16, you wrote: Still not working yet... Yes, thank you, I'll take you up on your offer of a configuration file. Here's /usr/local/etc/privoxy.sh. Remember, try just these two lines in /etc/rc.conf: privoxy_enable=YES privoxy_flags=-- user privoxy Pete ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Starting privoxy at startup
Oliver Iberien [EMAIL PROTECTED] wrote: Sorry to drag this out, but I still have not got this to work. I've looked at the permissions of the files involved but nothing untoward shows up. I think. There is just the conf file and the stuff in /var/log, right? How should their permissions look? If you comment out \ 1/dev/null 21 in the start script, Privoxy should give you a reason why it doesn't start. And no, Privoxy also needs at least read access to the filter and action files. Read access to the templates will be appreciated as well, but shouldn't cause start problems. You probably want Privoxy to be able to write to the action files, otherwise you can't modify them with the web interface. If I wanted to have two flags for privoxy in rc.conf -- the one below and one pointing to /usr/local/etc/privoxy/conf -- what would that look like? I believe you can change the configfile only in the start script itself. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Starting privoxy at startup
I can start privoxy manually with /usr/local/sbin/privoxy /usr/local/etc/privoxy/config I added this to /etc/rc.conf: privoxy_enable=YES privoxy_flags=/usr/local/etc/privoxy/config but that does not seem to do it. I tried putting a link in /etc/rc.d/ to the privoxy.sh in /usr/local/etc/rc.d, but that didn't do it, either. How do I get it to start? Thanks, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Starting privoxy at startup
Oliver Iberien wrote: I can start privoxy manually with /usr/local/sbin/privoxy /usr/local/etc/privoxy/config I added this to /etc/rc.conf: privoxy_enable=YES privoxy_flags=/usr/local/etc/privoxy/config but that does not seem to do it. I tried putting a link in /etc/rc.d/ to the privoxy.sh in /usr/local/etc/rc.d, but that didn't do it, either. How do I get it to start? When I installed privoxy from ports a shell script was placed in /usr/local/etc/rc.d, which does the job. Mine is mode 555. I'll e-mail you a copy if you want. I wouldn't link from /etc/rc.d -- bad mojo. I put the following two variables in /etc/rc.conf, and privoxy finds it's configuration files in the directory /usr/local/etc/privoxy/ without any help. There is more than one configuration file, and they are substantially self documenting. privoxy_enable=YES privoxy_flags=-- user privoxy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Starting privoxy at startup
Still not working yet... Yes, thank you, I'll take you up on your offer of a configuration file. Oliver On Sunday 26 March 2006 03:16, Pete Slagle wrote: Oliver Iberien wrote: I can start privoxy manually with /usr/local/sbin/privoxy /usr/local/etc/privoxy/config I added this to /etc/rc.conf: privoxy_enable=YES privoxy_flags=/usr/local/etc/privoxy/config but that does not seem to do it. I tried putting a link in /etc/rc.d/ to the privoxy.sh in /usr/local/etc/rc.d, but that didn't do it, either. How do I get it to start? When I installed privoxy from ports a shell script was placed in /usr/local/etc/rc.d, which does the job. Mine is mode 555. I'll e-mail you a copy if you want. I wouldn't link from /etc/rc.d -- bad mojo. I put the following two variables in /etc/rc.conf, and privoxy finds it's configuration files in the directory /usr/local/etc/privoxy/ without any help. There is more than one configuration file, and they are substantially self documenting. privoxy_enable=YES privoxy_flags=-- user privoxy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]