Paolo Pedroni wrote:
> Several times wrong, I'm afraid. It happens even with my 2.1 KDE, and
> with scripts as well, and it didn't happen with my fresh 8.0 install but
> only after I installed ppp-2.4.1, or some new version of initscripts
> (which I sadly installed together, thus not knowing which caused the
> bug).
> IMHO it may be some of the scripts in /etc/sysconfig/networking, which
> handle the renaming and switching of resolv.conf to deal with dynamic
> DNS configuration. Sadly I'm not good enough at bash scripting to be of
> any help.
>
If you come o Moscow you get beer from me :-)
The imediate problem was ip-down ppp script. I do not know, who resets
umask, but obviously when this script runs umask is set to at least 066
if not 077.
The following trivial patch shows that it is really the problem:
--- etc/ppp/ip-down.org Sat Aug 25 02:52:06 2001
+++ etc/ppp/ip-down Wed Aug 29 22:17:13 2001
@@ -9,6 +9,7 @@
export PATH=/sbin:/usr/sbin:/bin:/usr/bin
mv -f /etc/resolv.conf /etc/resolv.conf.tmp
+umask 022
cat /etc/resolv.conf.tmp | awk '{if(!/nameserver .* # ppp temp
entry.*/) print $0}' > /etc/resolv.conf
rm -f /etc/resolv.conf.tmp
The patch is just proof of concept. Note, that ip-down should at least
check, if any temporary entries really exist (it sdoes not help if you
configured with draknet and then started kppp. In this case first ppp
creates temporary entries and then kppp :-). Second, it leaves group as
user that run kppp - it is bug as well, it must reset group.
That's said, there may well be possible that standalone pppd has this
bug as well.
-andrej
