I was trying to remove some old, unused packages on one Digital Unix
4.0F system here (I wanted to remove "IAFWTCPW340", which is "TCP
Wrapper V7.6 Access control for Internet services"). I did "setld -d
IAFWTCPW340". As it printed some messages, it included things like
"awk: not found", "sed: not found", "basename: not found" that alarmed
me a little bit. So when it finished, I did "ls /usr/bin" and got "ls:
not found". For some reason, setld removed every file under /usr/bin!
Then I found out that Arkeia (the backup program we use) had decided not
to backup /usr/bin on this server. :-(
I copied /usr/bin from another DU 4.0F system and made the changes I
could remember, and it seems to be back okay.
Does anyone have any idea why this would happen though? This is really
the first time I've tried to use setld to remove a package. It
definately removed it (it doesn't show it as "installed" anymore), but
why did it wipe out /usr/bin? I was lucky I had GNU tar in
/usr/local/bin and still had my root shell, as login, sh, tar, etc. were
all gone.
--
Chris Adams <cmadams_at_hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
Received on Tue Dec 05 2000 - 16:18:56 NZDT