[Cooker] Network cannot resolve dns addresses again after last nights update

[Steve Morris-5]

After last nights urpmi --auto-update terminated about half way through,
the network can no longer resolve dns addresses from dhcp and the
nameserver entry has been removed. By modifying the network
configuration through drakconf, unselecting resolve dns addresses from
dhcp, and hard coding the primary dns address to the modem/routers ip
address, and restarting the network I was able to get to the internet again.
What is causing the nameserver entry to be removed? The last set of
packages installed is specified in the thread I raised about the update
failure, which by the way has also caused selecting kde4 from kdm to
actually launch kde3.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Frank Griffin-4]

Steve Morris wrote:
> After last nights urpmi --auto-update terminated about half way
> through, the network can no longer resolve dns addresses from dhcp and
> the nameserver entry has been removed.

Assuming that you don't have some manual, i.e. non-urpmi, procedure in
your update sequence, the fact that this only seems to happen to you
would suggest that you have some old, essentially unmaintained, package
installed that no one else does, and that its RPM scripts are at fault.

All I can suggest (other than a search of the package sources for
"resolv") is to capture the output of your updates over time, and look
for either signs that resolv.conf is being modified, or packages that
are changed only in the problem cases.

[Frank Griffin-4]

Steve Morris wrote:
> After last nights urpmi --auto-update terminated about half way
> through, the network can no longer resolve dns addresses from dhcp and
> the nameserver entry has been removed.
This was asked way earlier on, but which packages were installed
following the last successful package download before the error ?

[Steve Morris-5]

Frank Griffin wrote:

> Steve Morris wrote:
>> After last nights urpmi --auto-update terminated about half way
>> through, the network can no longer resolve dns addresses from dhcp
>> and the nameserver entry has been removed.
>
> Assuming that you don't have some manual, i.e. non-urpmi, procedure in
> your update sequence, the fact that this only seems to happen to you
> would suggest that you have some old, essentially unmaintained,
> package installed that no one else does, and that its RPM scripts are
> at fault.
>
> All I can suggest (other than a search of the package sources for
> "resolv") is to capture the output of your updates over time, and look
> for either signs that resolv.conf is being modified, or packages that
> are changed only in the problem cases.

Thanks Frank, I will check it out. This system started as a fresh

install of 2007.0, and was updated via cooker ever since, so it is
possible there is some old package there somewhere.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Steve Morris-5]

Frank Griffin wrote:
> Steve Morris wrote:
>> After last nights urpmi --auto-update terminated about half way
>> through, the network can no longer resolve dns addresses from dhcp
>> and the nameserver entry has been removed.
> This was asked way earlier on, but which packages were installed
> following the last successful package download before the error ?
>
Sorry Frank, I don't know at this stage as I was not able to figure out
how to copy to the clipboard from eterm. I am attempting the upgrade
again after hopefully having resolved the issue that was causing the
install to fail. If the problem reoccurs I should be able to get a list
of the packages installed.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

Steve Morris wrote:

> Frank Griffin wrote:
>> Steve Morris wrote:
>>> After last nights urpmi --auto-update terminated about half way
>>> through, the network can no longer resolve dns addresses from dhcp
>>> and the nameserver entry has been removed.
>> This was asked way earlier on, but which packages were installed
>> following the last successful package download before the error ?
>>
> Sorry Frank, I don't know at this stage as I was not able to figure out
> how to copy to the clipboard from eterm.

What has it to do with clipboard or eterm?

{pts/0}% sudo fgrep '[RPM]' /var/log/messages

May 20 00:44:37 cooker perl: [RPM] libpopt0-1.10.8-14mdv2009.0 installed
May 20 00:44:53 cooker perl: [RPM] librpm4.4-4.4.2.3-1mnb2 installed
May 20 00:45:10 cooker perl: [RPM] rpm-4.4.2.3-1mnb2 installed
May 20 00:45:11 cooker perl: [RPM] libpopt-devel-1.10.8-14mdv2009.0
installed
May 20 00:45:21 cooker perl: [RPM] rpm-build-4.4.2.3-1mnb2 installed
May 20 00:45:23 cooker perl: [RPM] python-rpm-4.4.2.3-1mnb2 installed
May 20 00:45:24 cooker perl: [RPM] libpopt-devel-1.10.8-13mdv2008.1 removed
May 20 00:45:26 cooker perl: [RPM] libpopt0-1.10.8-13mdv2008.1 removed
.. etc

[Steve Morris-5]

Andrey Borzenkov wrote:

> Steve Morris wrote:
>
>  
>> Frank Griffin wrote:
>>    
>>> Steve Morris wrote:
>>>      
>>>> After last nights urpmi --auto-update terminated about half way
>>>> through, the network can no longer resolve dns addresses from dhcp
>>>> and the nameserver entry has been removed.
>>>>        
>>> This was asked way earlier on, but which packages were installed
>>> following the last successful package download before the error ?
>>>
>>>      
>> Sorry Frank, I don't know at this stage as I was not able to figure out
>> how to copy to the clipboard from eterm.
>>    
>
> What has it to do with clipboard or eterm?
>
> {pts/0}% sudo fgrep '[RPM]' /var/log/messages
>
> May 20 00:44:37 cooker perl: [RPM] libpopt0-1.10.8-14mdv2009.0 installed
> May 20 00:44:53 cooker perl: [RPM] librpm4.4-4.4.2.3-1mnb2 installed
> May 20 00:45:10 cooker perl: [RPM] rpm-4.4.2.3-1mnb2 installed
> May 20 00:45:11 cooker perl: [RPM] libpopt-devel-1.10.8-14mdv2009.0
> installed
> May 20 00:45:21 cooker perl: [RPM] rpm-build-4.4.2.3-1mnb2 installed
> May 20 00:45:23 cooker perl: [RPM] python-rpm-4.4.2.3-1mnb2 installed
> May 20 00:45:24 cooker perl: [RPM] libpopt-devel-1.10.8-13mdv2008.1 removed
> May 20 00:45:26 cooker perl: [RPM] libpopt0-1.10.8-13mdv2008.1 removed
> .. etc
>
>  

Thanks Andrey, the issue with eterm was that was the shell tool I was

using as because of kde4/kde3 migration issues konsole was not in the
kde3 menus, and eterm didn't appear to provide copy facilities.
I wasn't aware that these messages were logged to this file, which also
raises another question I have been pondering. Why do we have so many
log files, why do we not use just syslog?

regards,
Steve

>
>  

[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Colin Guthrie-8]

Steve Morris wrote:
> I wasn't aware that these messages were logged to this file, which also
> raises another question I have been pondering. Why do we have so many
> log files, why do we not use just syslog?

Erm, this *is* going through syslog....

The syslog configuration (/etc/syslog.conf) determins how the various
messages are split out into separate files for convenience. I sure as
hell wouldn't want all my mail+firewall messages going into one big
file... Separate is good.

Col


--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Steve Morris-5]

Colin Guthrie wrote:

> Steve Morris wrote:
>> I wasn't aware that these messages were logged to this file, which
>> also raises another question I have been pondering. Why do we have so
>> many log files, why do we not use just syslog?
>
> Erm, this *is* going through syslog....
>
> The syslog configuration (/etc/syslog.conf) determins how the various
> messages are split out into separate files for convenience. I sure as
> hell wouldn't want all my mail+firewall messages going into one big
> file... Separate is good.

Except for forensic investigation, unless you know exactly which of the

various files contains a specific message.

regards,
Steve

>
> Col
>
>

[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Colin Guthrie-8]

Steve Morris wrote:

> Colin Guthrie wrote:
>> Steve Morris wrote:
>>> I wasn't aware that these messages were logged to this file, which
>>> also raises another question I have been pondering. Why do we have so
>>> many log files, why do we not use just syslog?
>>
>> Erm, this *is* going through syslog....
>>
>> The syslog configuration (/etc/syslog.conf) determins how the various
>> messages are split out into separate files for convenience. I sure as
>> hell wouldn't want all my mail+firewall messages going into one big
>> file... Separate is good.
> Except for forensic investigation, unless you know exactly which of the
> various files contains a specific message.

If you plan on doing that, just configure your syslog.conf to put
everything in one file... e.g. /var/log/syslog..... I really wish
someone would do something sensible like that :p

Col

--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Michael Scherer-2]

Le mercredi 21 mai 2008 à 07:05 +1000, Steve Morris a écrit :

> Colin Guthrie wrote:
> > Steve Morris wrote:
> >> I wasn't aware that these messages were logged to this file, which
> >> also raises another question I have been pondering. Why do we have so
> >> many log files, why do we not use just syslog?
> >
> > Erm, this *is* going through syslog....
> >
> > The syslog configuration (/etc/syslog.conf) determins how the various
> > messages are split out into separate files for convenience. I sure as
> > hell wouldn't want all my mail+firewall messages going into one big
> > file... Separate is good.
> Except for forensic investigation, unless you know exactly which of the
> various files contains a specific message.

then you can either use  grep to search the proper file ( grep -r ), or
cat | sort  to get file in a file.

you can also modify syslog to log everything in one file :

*.* /var/log/everything

--
Michael scherer

[Steve Morris-5]

Colin Guthrie wrote:

> Steve Morris wrote:
>> Colin Guthrie wrote:
>>> Steve Morris wrote:
>>>> I wasn't aware that these messages were logged to this file, which
>>>> also raises another question I have been pondering. Why do we have
>>>> so many log files, why do we not use just syslog?
>>>
>>> Erm, this *is* going through syslog....
>>>
>>> The syslog configuration (/etc/syslog.conf) determins how the
>>> various messages are split out into separate files for convenience.
>>> I sure as hell wouldn't want all my mail+firewall messages going
>>> into one big file... Separate is good.
>> Except for forensic investigation, unless you know exactly which of
>> the various files contains a specific message.
>
> If you plan on doing that, just configure your syslog.conf to put
> everything in one file... e.g. /var/log/syslog..... I really wish
> someone would do something sensible like that :p
>
> Col
>

That would be ideal, but then we would also be doubling up on messages

in syslog, as I have seen messages that have been written
/var/log/syslog also witten to /var/log/messages, which to me seems a
waste of resources.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Steve Morris-5]

Michael Scherer wrote:

> Le mercredi 21 mai 2008 à 07:05 +1000, Steve Morris a écrit :
>  
>> Colin Guthrie wrote:
>>    
>>> Steve Morris wrote:
>>>      
>>>> I wasn't aware that these messages were logged to this file, which
>>>> also raises another question I have been pondering. Why do we have so
>>>> many log files, why do we not use just syslog?
>>>>        
>>> Erm, this *is* going through syslog....
>>>
>>> The syslog configuration (/etc/syslog.conf) determins how the various
>>> messages are split out into separate files for convenience. I sure as
>>> hell wouldn't want all my mail+firewall messages going into one big
>>> file... Separate is good.
>>>      
>> Except for forensic investigation, unless you know exactly which of the
>> various files contains a specific message.
>>    
>
> then you can either use  grep to search the proper file ( grep -r ), or
> cat | sort  to get file in a file.
>
> you can also modify syslog to log everything in one file :
>
> *.* /var/log/everything
>
>  

But that still leaves the issue of elmininating duplicate messages that

are written to multiple files, eg: to syslog and messages.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Colin Guthrie-8]

Steve Morris wrote:

> Colin Guthrie wrote:
>> Steve Morris wrote:
>>> Colin Guthrie wrote:
>>>> Steve Morris wrote:
>>>>> I wasn't aware that these messages were logged to this file, which
>>>>> also raises another question I have been pondering. Why do we have
>>>>> so many log files, why do we not use just syslog?
>>>>
>>>> Erm, this *is* going through syslog....
>>>>
>>>> The syslog configuration (/etc/syslog.conf) determins how the
>>>> various messages are split out into separate files for convenience.
>>>> I sure as hell wouldn't want all my mail+firewall messages going
>>>> into one big file... Separate is good.
>>> Except for forensic investigation, unless you know exactly which of
>>> the various files contains a specific message.
>>
>> If you plan on doing that, just configure your syslog.conf to put
>> everything in one file... e.g. /var/log/syslog..... I really wish
>> someone would do something sensible like that :p
>>
>> Col
>>
> That would be ideal, but then we would also be doubling up on messages
> in syslog, as I have seen messages that have been written
> /var/log/syslog also witten to /var/log/messages, which to me seems a
> waste of resources.

Well configure it differently. Personally I like this. Syslog contains
the majority of system messages, whereas all the others contain the
relevant subset. I personally find this pretty good as it pre-greps the
log files. Sure it uses a bit more disk space but it's not exactly a
problem for 99.9% of people and makes diagnostics many times easier as
it saves non-technical uses from wading through a pile of crap to get
the juicy tidbit.

For those that have limited diskspace, they will probably configure a
remote syslog (as I do on my network boot embedded systems), or
configure a cut down log.

Col

--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Colin Guthrie-8]

Steve Morris wrote:

> Michael Scherer wrote:
>> Le mercredi 21 mai 2008 à 07:05 +1000, Steve Morris a écrit :
>>  
>>> Colin Guthrie wrote:
>>>    
>>>> Steve Morris wrote:
>>>>      
>>>>> I wasn't aware that these messages were logged to this file, which
>>>>> also raises another question I have been pondering. Why do we have
>>>>> so many log files, why do we not use just syslog?
>>>>>        
>>>> Erm, this *is* going through syslog....
>>>>
>>>> The syslog configuration (/etc/syslog.conf) determins how the
>>>> various messages are split out into separate files for convenience.
>>>> I sure as hell wouldn't want all my mail+firewall messages going
>>>> into one big file... Separate is good.
>>>>      
>>> Except for forensic investigation, unless you know exactly which of
>>> the various files contains a specific message.
>>>    
>>
>> then you can either use  grep to search the proper file ( grep -r ), or
>> cat | sort  to get file in a file.
>>
>> you can also modify syslog to log everything in one file :
>>
>> *.* /var/log/everything
>>  
> But that still leaves the issue of elmininating duplicate messages that
> are written to multiple files, eg: to syslog and messages.

Duplicate messages are not a problem, it's the whole point ;)

If you want to write your syslog.conf like misc suggests and include
*only* that definition, you wont get the duplicates you're so worried
about. Personally, I don't give a monkeys about the duplicate and am
very happy when having to do forensics (especially when in a hurry) to
have things split up nicely for me.

Col

--

+--------------------------+
|      Colin Guthrie       |
+--------------------------+
| cguthrie(at)mandriva.org |
|  http://colin.guthr.ie/  |
+--------------------------+

[Steve Morris-5]

Colin Guthrie wrote:

> Steve Morris wrote:
>> Colin Guthrie wrote:
>>> Steve Morris wrote:
>>>> Colin Guthrie wrote:
>>>>> Steve Morris wrote:
>>>>>> I wasn't aware that these messages were logged to this file,
>>>>>> which also raises another question I have been pondering. Why do
>>>>>> we have so many log files, why do we not use just syslog?
>>>>>
>>>>> Erm, this *is* going through syslog....
>>>>>
>>>>> The syslog configuration (/etc/syslog.conf) determins how the
>>>>> various messages are split out into separate files for
>>>>> convenience. I sure as hell wouldn't want all my mail+firewall
>>>>> messages going into one big file... Separate is good.
>>>> Except for forensic investigation, unless you know exactly which of
>>>> the various files contains a specific message.
>>>
>>> If you plan on doing that, just configure your syslog.conf to put
>>> everything in one file... e.g. /var/log/syslog..... I really wish
>>> someone would do something sensible like that :p
>>>
>>> Col
>>>
>> That would be ideal, but then we would also be doubling up on
>> messages in syslog, as I have seen messages that have been written
>> /var/log/syslog also witten to /var/log/messages, which to me seems a
>> waste of resources.
>
> Well configure it differently. Personally I like this. Syslog contains
> the majority of system messages, whereas all the others contain the
> relevant subset. I personally find this pretty good as it pre-greps
> the log files. Sure it uses a bit more disk space but it's not exactly
> a problem for 99.9% of people and makes diagnostics many times easier
> as it saves non-technical uses from wading through a pile of crap to
> get the juicy tidbit.
>
> For those that have limited diskspace, they will probably configure a
> remote syslog (as I do on my network boot embedded systems), or
> configure a cut down log.
>
> Col
>

Point taken. I guess being an ex mainframe sysprog I am used to syslog

being the definitive source for logs, and having to trawl through
multiple "log files" trying to find info for problems frustrates me,
particularly when I don't know what/where to make your suggested
changes, and even if I did I may not necessarily know enough about the
script environment used to make changes without stuffing it up.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Michael Scherer-2]

Le jeudi 22 mai 2008 à 09:48 +0100, Colin Guthrie a écrit :

> Steve Morris wrote:
> > Colin Guthrie wrote:
> >> Steve Morris wrote:
> >>> Colin Guthrie wrote:
> >>>> Steve Morris wrote:
> >>>>> I wasn't aware that these messages were logged to this file, which
> >>>>> also raises another question I have been pondering. Why do we have
> >>>>> so many log files, why do we not use just syslog?
> >>>>
> >>>> Erm, this *is* going through syslog....
> >>>>
> >>>> The syslog configuration (/etc/syslog.conf) determins how the
> >>>> various messages are split out into separate files for convenience.
> >>>> I sure as hell wouldn't want all my mail+firewall messages going
> >>>> into one big file... Separate is good.
> >>> Except for forensic investigation, unless you know exactly which of
> >>> the various files contains a specific message.
> >>
> >> If you plan on doing that, just configure your syslog.conf to put
> >> everything in one file... e.g. /var/log/syslog..... I really wish
> >> someone would do something sensible like that :p
> >>
> >> Col
> >>
> > That would be ideal, but then we would also be doubling up on messages
> > in syslog, as I have seen messages that have been written
> > /var/log/syslog also witten to /var/log/messages, which to me seems a
> > waste of resources.
>
> Well configure it differently. Personally I like this. Syslog contains
> the majority of system messages, whereas all the others contain the
> relevant subset. I personally find this pretty good as it pre-greps the
> log files. Sure it uses a bit more disk space but it's not exactly a
> problem for 99.9% of people and makes diagnostics many times easier as
> it saves non-technical uses from wading through a pile of crap to get
> the juicy tidbit.

It also double the number of thing to be written in log, on the disk.
And that can be a big problem on a busy server.

--
Michael Scherer

[Frank Griffin-4]

Steve Morris wrote:
> Point taken. I guess being an ex mainframe sysprog I am used to syslog
> being the definitive source for logs, and having to trawl through
> multiple "log files" trying to find info for problems frustrates me,
> particularly when I don't know what/where to make your suggested
> changes, and even if I did I may not necessarily know enough about the
> script environment used to make changes without stuffing it up.

man syslog.conf

[Steve Morris-5]

Frank Griffin wrote:

> Steve Morris wrote:
>> Point taken. I guess being an ex mainframe sysprog I am used to
>> syslog being the definitive source for logs, and having to trawl
>> through multiple "log files" trying to find info for problems
>> frustrates me, particularly when I don't know what/where to make your
>> suggested changes, and even if I did I may not necessarily know
>> enough about the script environment used to make changes without
>> stuffing it up.
>
> man syslog.conf
>
>

Thanks Frank, I'll take a look, I just assumed it was script based.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Steve Morris-5]

I have just attempted a cooker update and received the following errors:

   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/libgle3-3.1.0-7mdv2009.0.i586.rpm
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/kdemultimedia4-core-4.0.74-2mdv2009.0.i586.rpm
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/rpmdrake-4.9.15-1mdv2009.0.noarch.rpm
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/kmix-4.0.74-2mdv2009.0.i586.rpm
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/drakconf-icons-10.18.6-1mdv2009.0.i586.rpm
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/libfreebob0-1.0.7-2mdv2009.0.i586.rpm
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/drakconf-10.18.6-1mdv2009.0.i586.rpm
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/ruby-1.8.6-12p114mdv2009.0.i586.rpm
installing libgle3-3.1.0-7mdv2009.0.i586.rpm
rpmdrake-4.9.15-1mdv2009.0.noarch.rpm
kdemultimedia4-core-4.0.74-2mdv2009.0.i586.rpm
kmix-4.0.74-2mdv2009.0.i586.rpm
drakconf-icons-10.18.6-1mdv2009.0.i586.rpm
libfreebob0-1.0.7-2mdv2009.0.i586.rpm
drakconf-10.18.6-1mdv2009.0.i586.rpm ruby-1.8.6-12p114mdv2009.0.i586.rpm
from /var/cache/urpmi/rpms
Preparing...                    
#########################################################################################################################
    23/61: kdemultimedia4-core  
#########################################################################################################################
    24/61: kmix                  
#########################################################################################################################
    25/61: ruby                  
#########################################################################################################################
    26/61: drakconf-icons        
#########################################################################################################################
    27/61: rpmdrake              
#########################################################################################################################
    28/61: libgle3              
#########################################################################################################################
    29/61: libfreebob0          
#########################################################################################################################
    30/61: drakconf              
#########################################################################################################################

   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/dragonplayer-4.0.74-2mdv2009.0.i586.rpm
...retrieving failed: curl: (6) Couldn't resolve host 'fr2.rpmfind.net'
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/akonadi-common-0.81.0-0.811818.1mdv2009.0.i586.rpm
...retrieving failed: curl: (28) Connection time-out
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/akonadi-devel-0.81.0-0.811818.1mdv2009.0.i586.rpm
...retrieving failed: curl: (28) Connection time-out
   
ftp://fr2.rpmfind.net/linux/Mandrakelinux/devel/cooker/i586/media/main/release/kscd-4.0.74-2mdv2009.0.i586.rpm
...retrieving failed: curl: (28) Connection time-out

I have checked /etc/resolv.conf and the nameserver statement is still
there, and, /var/run/resolvconf/interface/eth0 still exists and contains
the nameserver statement. Could this be an indication of where my dns
failures are originating from?

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---