When using pppd with squid the permissions on /etc/resolv.conf get changed to 640. The rc init script /etc/init.d/net.ppp0 echos the command "chmod 640 /etc/resolv.conf" into /etc/ppp/ip-up, which causes the permissions on /etc/resolv.conf to be changed to 640 when the connection comes up. This causes squid to die or not start at all. Running 'squid -N -d 1' shows the following: 2003/07/28 21:31:14| Starting Squid Cache version 2.5.STABLE3 for i686-pc-linux-gnu... 2003/07/28 21:31:14| Process ID 2075 2003/07/28 21:31:14| With 1024 file descriptors available 2003/07/28 21:31:14| Performing DNS Tests... 2003/07/28 21:31:14| Successful DNS name lookup tests... 2003/07/28 21:31:14| DNS Socket created at 0.0.0.0, port 1026, FD 4 2003/07/28 21:31:14| /etc/resolv.conf: (13) Permission denied FATAL: Could not find any nameservers. Please check your /etc/resolv.conf file or use the 'dns_nameservers' option in squid.conf. Aborted ===== Reproducible: Always Steps to Reproduce: 1. Start the pppd daemon via /etc/init.d/net.ppp0 2. Establish an Internet connection. 3. Start the squid daemon via /etc/init.d/squid Actual Results: /var/log/daemon.log showed several failures for squid with the following final error: Jul 28 06:30:12 firewall squid[1073]: Exiting due to repeated, frequent failures Expected Results: Squid should be able to start and not die. The rc init script /etc/init.d/net.ppp0 should echo the command "chmod 644 /etc/resolv.conf" into /etc/ppp/ip-up. Also, if the permission are set to 640, users (except root) and non-root daemons can not do DNS lookups.
ls -la /etc/resolv.conf -rw-r--r-- 1 root root 103 Jun 25 15:59 /etc/resolv.conf must me something with ppp
Martin, know what Chuck Brewer's email is ? killian@g.o do not work, and he looks more after ppp these days ...
this caught me today when setting up my laptop to take on vacation... (yay) /etc/init.d/net.ppp0 does indeed chmod 640 /etc/resolv.conf and since /etc/resolv.conf's ownership is root:root no users can resolve names after bringing up the ppp link. I'd also propose chmod 644 in /etc/init.d/net.ppp0 I can't see an issue with resolv.conf keeping o+r perms, anyone else? also reported in bug 26311
This was biting me now. I ended up modifying /etc/init.d/net.ppp0 to chmod 644 before discovering this bug report. I see last activity here is from 2003-09-20 --- is anything blocking resolution (e.g. s/640/644/ )?
What about your umask in /etc/profile?
umask 022
The umask would have nothing to do with this problem because I determined the problem was because of the net.ppp0 rc init script.
what's your ppp version=
i think this is caused because you don't updated the net.ppp0 init.d file after updating ppp
