Hi everybody, back from a week in FL that included a trip to the Cape, nice to have kin with a pad in Mt. Dora.
I was running 2.4.3b3-20020311 at the time. I'd left amanda to fill the holding disk while I was gone, and it appeared to have had an access problem according to the mails because I had shut the gateway machine off while I was gone, which presumably was the target of amanda's gethostbyname activities. A couple of amflushes and that was cleaned up though, but I need someone to tell me the *right* syntax to have amflush /config/ do a thru c, then d thru the end, etc because apparently the only acceptable syntax was 'all'. And somehow, even that fit on one 4g tape....???? Then I toured the .ca site for new releases, finding 2.4.3b3-20020324 as the newest one, so I grabbed it, and built it, and installed it as per the usual configuration here. But it hangs while doing '/usr/local/libexec/chg-scsi -info' (don't take the above path as gospel, I've driven 1100 miles in the last 24 hrs) with that process using 86% of the cpu, apparently forever, or until a ctrl c is applied. Kinda slows up setiathome though. :-) Re-installing amanda-2.4.3b3-20020311 seems to bring things back to normal. Didja change something in the chg-scsi.conf requirements column while I was out getting some sand in my shoes? Or is this just the usual beta testing squiggle? -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.7+% setiathome rank, not too shabby for a hillbilly
