Hi,
>Did you get all an unending stream of error messages about the harddrive
>when you had to reboot to get a prompt? The computer that I just had the
>hard drive and mother board replaced always generated error messages
>when cron ran slocate. I removed slocate from cron.daily and didn't have
>anymore messages until recently when I got a constant stream of error
>messages and couldn't login. I was able to fix the filesystem but was
>worried about my harddrive. In my case when I sent the information
>generated
>by hdparm to seagate they told me that bios auto feature had set up the
>drive geometry incorrectly. Maybe you have a similar problem.
> Linda
When I ran slocate there was a Segmentation Fault and my prompt never
returned. I used the -u switch I got from an email "tip." After that, I
could logon, but would never get to a prompt. The shell just sat there. I
tried a number of things to get at the system: virtual consoles, rlogin,
rsh. All failed, yet the name server running on the box was fine. At
first I could get a ps from rsh, but that started failing. My uptime was
343 days, and I hated to do the reset.
When I rebooted, I was advised to run fsck. I did so and took the <y>
option on quite a few (10 or so) fixes. When I finally rebooted, I got the
error messages mentioned and the NFS stuff didn't start.
I am not running slocate from cron.
Getting connected with telnet takes much longer, but once you're in, all seems
well.
Thanks,
-Tom
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
