This is not a problem, per se, but it Should Not Happen . When I launch
amrecover from a directory which is in the disklist I get this:
[root@moby admin]# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on backup ...
220 moby AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2002-04-25)
200 Working date set to 2002-04-25.
200 Config set to Daily.
200 Dump host set to moby.
Can't determine disk and mount point from $CWD
amrecover> lpwd
/export/moby/admin
I can't use amrecover until I run "setdisk /export/moby/admin". After
that it works like a million bucks. It's been a while since I ran a
restore so I had forgotten about this behavior, but I just was reminded
of how annoying it is. What can be done about amrecover not knowing
what the CWD is?
--
Brandon D. Valentine <[EMAIL PROTECTED]>
Computer Geek, Center for Structural Biology
"This isn't rocket science -- but it _is_ computer science."
- Terry Lambert on [EMAIL PROTECTED]
