(ask) about squid3 need to restart every time booting (LMDE)
Posted: Mon Mar 14, 2011 10:58 am
Hi ,
I have install squid3 for my pc . The only problem that appear is that every time after booting , squid3 wont work and need to restarted manually using
' /etc/init.d/squid3 restart ' .
I have been googling at this and still find no solution (any solution i found like cp to dispatcher have been used but still no luck ) . my problem seem like identic to te problem in this link , https://bugzilla.redhat.com/show_bug.cgi?id=453304
a little bit copy paste from the site :
"
The problem is that squid uses resolv.conf to load nameservers by default and
the NetworkManager re-create resolv.conf during each starting.
The clearest way to fix the problem is to use dns_nameservers option in the
squid.conf file and to put there servers that are in the resolv.conf file.
This is not a bug of squid because the squid can't affect resolv.conf creation
and the one provides resources to fix the problem.
These findings could be read from /var/log/squid/cache.log file.
"
I am using latest stable squid3 package on squeeze .
edit Start script at /etc/rc.local have been used and still no luck .
startup application / automatic launcher have been used and still no luck .
anybody know the workaround for this ?
Tq
I have install squid3 for my pc . The only problem that appear is that every time after booting , squid3 wont work and need to restarted manually using
' /etc/init.d/squid3 restart ' .
I have been googling at this and still find no solution (any solution i found like cp to dispatcher have been used but still no luck ) . my problem seem like identic to te problem in this link , https://bugzilla.redhat.com/show_bug.cgi?id=453304
a little bit copy paste from the site :
"
The problem is that squid uses resolv.conf to load nameservers by default and
the NetworkManager re-create resolv.conf during each starting.
The clearest way to fix the problem is to use dns_nameservers option in the
squid.conf file and to put there servers that are in the resolv.conf file.
This is not a bug of squid because the squid can't affect resolv.conf creation
and the one provides resources to fix the problem.
These findings could be read from /var/log/squid/cache.log file.
"
I am using latest stable squid3 package on squeeze .
edit Start script at /etc/rc.local have been used and still no luck .
startup application / automatic launcher have been used and still no luck .
anybody know the workaround for this ?
Tq