Eh, actually I've seen this myself.
It was NOT a hardware problem at all.
Rather one of the local services was not "turned on" during installation.
I went thru the services list and turned on several daemons and installed the
appropriate RPM's for Telnet, etc.
Afterwards the message disappeared on the next reboot.
It seems to be related to networking setup and affected the X server as well...
apparently having something to do with authentication.
I'm sorry for not being more specific, but the problem went away so quickly after this
that I did not dig any deeper...
-JMS
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of civileme
Sent: Monday, January 01, 2001 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: [expert] Critical problem
On Monday 01 January 2001 17:44, you wrote:
> Hi:
>
> I had hoped never to see this, but I got the following message (when
> logged on as root):
>
> <daemon.crit> mon[1256]: failure for servers telnet 978304853 localhost
>
> does anyone know what this means.
>
Well, it sounds like Christmas was a little early for the new hardware you
will need. Most likely it is memory, but it might be HDD.
Civileme
> Fortunately, I got rattled and was able to make a backup of all the
> data. Now the PC won't boot. It had been having trouble in the boot
> process, reverting to level 3 and not starting X (as it should have).
> It was from the command line that I was able to back up my files. Now,
> she won't boot, even from the boot floppy.
>
> Does anyone know what the problem could be?
>
> Ron
> ./.
