I didn't write all of them down, it was a screen full, looked like memory
addresses. It just said that it couldn't run /usr/sbin/updatedb. This is the
first time that this has ever happened. The box was up for 132 days, then this
happened. I've had the box up longer than that before without problems. I
haven't changed anything in the past month.
On Sat, 21 Apr 2001, Matthew Melvin wrote:
--On Sat, 21 Apr 2001 at 9:36am (-0400), Jake McHenry wrote:
--
-->
--> what is it?
-->
--> I got an error last night that locked up my machine, said that it could
--> not run /usr/bin/updatedb and gave me a bunch of error info. Does anyone
--> know if I can turn this service off so that I don't get this again?
-->
--
--Perhaps you could tell us more the 'bunch of errors'? If it locked up your
--machine I'd be inclined to think that not being able to run updatedb was
--another symptom and not the cause.
--
--M.
--
----
--WebCentral Pty Ltd Australia's #1 Internet Web Hosting Company
--Level 1, 96 Lytton Road. Network Operations - Systems Engineer
--PO Box 4169, East Brisbane. phone: +61 7 3249 2557
--Queensland, Australia. pgp key id: 0x900E515F
--
--
--
--_______________________________________________
--Redhat-list mailing list
[EMAIL PROTECTED]
--https://listman.redhat.com/mailman/listinfo/redhat-list
--
Jake McHenry
[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
