Tim wrote:
> On Thu, 2010-07-08 at 09:09 -0700, Jason Turning wrote:
>> It's on for runlevels 2 thru 5, but on boot up it fails with the
>> following message from the Privoxy logfile:
>>
>> Jul 08 09:02:21.415 7f27343cd700 Fatal error: can't bind to 127.0.0.1:8118:
>> The hostname is not resolva
On Thu, 2010-07-08 at 09:09 -0700, Jason Turning wrote:
> It's on for runlevels 2 thru 5, but on boot up it fails with the
> following message from the Privoxy logfile:
>
> Jul 08 09:02:21.415 7f27343cd700 Fatal error: can't bind to 127.0.0.1:8118:
> The hostname is not resolvable
>
> So I'm g
Natxo Asenjo wrote:
> On Thu, Jul 8, 2010 at 7:21 AM, Jason Turning wrote:
>> I just upgraded my laptop to Fedora 12, and now Privoxy is failing on bootup
>> and has to be manually started. Anyone encountered this problem, and if so
>> what
>> was the fix?
>
> what does
>
> $/sbin/chkconfig --l
On Thu, Jul 8, 2010 at 7:21 AM, Jason Turning wrote:
>
> I just upgraded my laptop to Fedora 12, and now Privoxy is failing on bootup
> and has to be manually started. Anyone encountered this problem, and if so
> what
> was the fix?
what does
$/sbin/chkconfig --list privoxy
tell you?
It shoul
I just upgraded my laptop to Fedora 12, and now Privoxy is failing on bootup
and has to be manually started. Anyone encountered this problem, and if so what
was the fix?
Thanks.
Jason
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin