Hi
On Thu, 14 Sep 2000, Statux wrote:
> Have you run /sbin/fsck.ext2 ?
of course, but usually through e2fsck.
> > Does anyone have any idea what might be corrupted here? /etc/rc.d/rc
> > exists and is executable. All the other scripts and directories under
> > /etc/rc.d look fine too. In fact I restored /etc from backups, and this
> > still happens.
>
> permissions correct? How's /etc/fstab?
fine
>
> > If it turns out the disk is fine, I'd hate to have to rebuild this OS, so
> > it would be nice if I could fix this.
>
> How old is the equipment in your box?
mmh. the RAM would be about 2 years, perhaps 2.5 aong with the mb/cpu.
Disk can be no older than 1.5 years.
> > dlerror: /some/lib.so:failed to map a segment from shared object: Cannot
> > allocate memory
>
> Yeah.. I think the two errors are related. How's your RAM? Physically and
> as far as Linux is concerned? How much do you have, etc?
256 MB, 256MB swap. Again, the physical RAM is nowhere near used up, and
hardly any swap is ever used. This is really a waaaay overpowered system
for it's use in a small office.
>
> Do you have program crashes, etc?
not that I am aware of, but it's usually 1K miles away and I only hear
about it when it's not working :).
> > How can I test this machine? I'll run memtest86 on it to check the RAM,
> > but how to I stress test the disks? I could compile the kernel ina loop
> > for a while. Anything else?
memtest 86 had run for about 6 hours when I left hoem this morning, 6
successful passes.
>
> Use the /sbin/fsck.ext2 program and read the man page for details. Check
> /sbin for other utilities (it's a cool place for that sort of thing) :)
I'm not sure what you expect this will do fo me other than help recover
the filesystem when it gets f*ked. I have done so, but it's currently
still got a problem anyway. I need to test the hardware, not the software.
any more ideas?
thanks
charles
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
