by rogerd.. » Mon, 11 Sep 2000 09:18:23
I "newfs"ed each partition then did a ufsrestore on each...
The box ran for a week, then died again w/the same errors.
Seeing lots of posts w/similar problems w/the ld.so.1.
Why didn't the ufsrestore fix it?
Is there a virus going 'round?
-curious
Sent via Deja.com http://www.deja.com/
Before you buy.
by Alan Coopersmit » Mon, 11 Sep 2000 14:00:02
If your box was able to run for a week then you had to have a working
ld.so.1. Are you sure nothing you're doing or in a cron job is killing
it?
--
________________________________________________________________________
Working for, but definitely not speaking for, Sun Microsystems, Inc.
1. ufsrestore... doesn't. Why ?
We are trying to restore a directory that was dumped to tape with
ufsdump. We are using ufsrestore to do it. In interactive mode, ufsrestore
begins restoring the directory from tape, but then starts to produce
error messages regarding "filename too long" etc. It fails to restore
the listed files and then... Segmentation Fault/Core dump.
We've got Solaris_2.3. Anyone ever seen this before ? Are we missing a
patch to ufsrestore or something ?
Any help would be greatly appreciated. Thank you, Ralph Osborne
3. Why doesn't somebody fix who?
5. Why doesn't Redhat fix it ??????
6. Weird problems: Masqued machines work, Masq server can't.
7. iptables doesn't support mangle table
9. Why won't ld traverse it's "standard" path?
10. Why doesn't sed 's/$/^M/' work as expected?
12. Why doesn't reboot do a 'swapoff -a' ????
13. Why: perl -e <<'EOF' doesn't work (bash)