Hello Peter,
I too was puzzled. The daemon would immediately exit. I ran it from
the command line and found that the configuration wasn't quite complete.
Hint: to run it from the terminal window:
1. cd /opt/local/etc/privoxy
2. make the files in that directory readable and executable
3. simply run it from the shell:
privoxy --no-daemon
What I found was that the macports build script does not do a step the
privoxy installer does, backup the "default.action" and copy
default.action.master over default.action.
So, I downloaded the 3.0.12 source for privoxy, untar'd it, and copied
the default.action.master file into /opt/local/etc/privoxy/
default.action
I found this out when Snow Leopard became the hot topic, and I
neglected to write a ticket on this. Some action needs to be taken to
get it to start up without this manual configuration twiddling.
I'm at a loss what the correct build script action should be. At a
minimum it should copy default.action.master to /opt/local/etc/privoxy
and give the user a clue that it needs renaming to default.action
Any other ideas on how to resolve this from others more experienced
with macports?
David
On Oct 13, 2009, at 7:00 AM, macports-users-
[email protected] wrote:
Message: 2
Date: Mon, 12 Oct 2009 15:04:20 +0100 (CET)
From: Peter Krefting <[email protected]>
To: [email protected]
Subject: MacPorts privoxy and autostart on Snow Leopard
Message-ID: <[email protected]>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Hi!
I switched my Privoxy installation over to use the MacPorts version
because I
had problems autostarting the "official" Mac version after upgrading
to Leopard
and Snow Leopard (I hacked around the autostart on Leopard, but it
stopped
working again).
After installing the version from MacPorts, it doesn't seem to
autostart
either, though. I am probably missing something vital here, and would
appreciate if someone could point me to how to set it up to
autostart (starting
on boot as a special "privoxy" user).
Thank you in advance,
--
\\// Peter - http://www.softwolves.pp.se/
------------------------------
Message: 3
Date: Mon, 12 Oct 2009 09:21:51 -0500
From: Ryan Schmidt <[email protected]>
To: Peter Krefting <[email protected]>
Cc: [email protected]
Subject: Re: MacPorts privoxy and autostart on Snow Leopard
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
On Oct 12, 2009, at 09:04, Peter Krefting wrote:
I switched my Privoxy installation over to use the MacPorts version
because I had problems autostarting the "official" Mac version after
upgrading to Leopard and Snow Leopard (I hacked around the autostart
on Leopard, but it stopped working again).
After installing the version from MacPorts, it doesn't seem to
autostart either, though. I am probably missing something vital
here, and would appreciate if someone could point me to how to set
it up to autostart (starting on boot as a special "privoxy" user).
What have you tried so far? Have you loaded the launchd plist? If so,
what command did you use to do that?
------------------------------
Message: 4
Date: Mon, 12 Oct 2009 10:05:32 -0500
From: Ryan Schmidt <[email protected]>
To: Fabrizio Bartolomucci <[email protected]>
Cc: MacPorts Users <[email protected]>
Subject: Re: Path problems
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
On Oct 12, 2009, at 10:02, Fabrizio Bartolomucci wrote:
Ryan Schmidt ha scritto:
On Oct 12, 2009, at 08:28, Rainer M?ller wrote:
Seems like you do not have Xcode installed which is a requirement
for
MacPorts. Please see <http://guide.macports.org/#installing.xcode>
Or if you do have Xcode installed, then perhaps you unchecked the
Unix Development checkbox in the Xcode installer package. If so,
reinstall Xcode, and do not deselect that checkbox, because it
installs /usr/bin/gcc-4.2 and other components required by MacPorts.
Actually I did nothing but installing Snow Leopard to discover
MacPorts did not like it so much...
MacPorts works great with Snow Leopard. Maybe you didn't upgrade your
Xcode to version 3.2? You need to do that. The Xcode 3.2 installer
package is on the Snow Leopard DVD.
P.S: Don't forget to use Reply All so your reply goes to the list too,
not just to me.
------------------------------
Message: 5
Date: Mon, 12 Oct 2009 17:10:50 +0200
From: Damien Clauzel <[email protected]>
To: MacPorts Users <[email protected]>
Subject: Re: MacPorts privoxy and autostart on Snow Leopard
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
Le 12 oct. 2009 ? 16:04, Peter Krefting a ?crit :
I switched my Privoxy installation over to use the MacPorts version
because I had problems autostarting the "official" Mac version after
upgrading to Leopard and Snow Leopard (I hacked around the autostart
on Leopard, but it stopped working again).
I am using this plist for launchd.
It lives in /Library/LaunchDaemons/fr.nom.Clauzel.privoxy.plist and
starts automatically privoxy on startup.
___
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd
">
<plist version="1.0">
<dict>
<key>Label</key>
<string>fr.nom.Clauzel.privoxy</string>
<key>OnDemand</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/opt/local/sbin/privoxy</string>
<string>--no-daemon</string>
<string>/opt/local/etc/privoxy/config</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>UserName</key>
<string>privoxy</string>
<key>GroupName</key>
<string>privoxy</string>
<key>ServiceDescription</key>
<string>dClauzel privoxy serveur</string>
</dict>
</plist>
___
I know that some people use daemondo, but I have never see the point
of using this tool for managing processes; launched does everything
that is needed.
Cheers,
Damien
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
