On Tue, 7 Nov 2000, Nathan Bird wrote:
In disklist I was under the impression that you had to write the following.
hostname diskdev dumptype [spindle [interface]]
The diskdev that it is referring to is the tape device isn't it?
Nice idea :-)
No, "diskdev" is the harddisk (sig!) on the
On Thu, 2 Nov 2000, Denise Ives wrote:
Looks like there is no problem with client connections -
but the subject header does have this BOLD warning message.
Can this be ignored?
No! You don't have a problem with your client connections, as you
realized. But have a look at the server
Sorry, wrong mailinglist address on the first try.
-- Forwarded message --
Date: Fri, 3 Nov 2000 13:31:34 +0100 (CET)
From: Peter Schaffrath [EMAIL PROTECTED]
To: Denise Ives [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: back to square 1
Hi Denise!
One point first: make
Anyone out there used to such strange messages? I'm also curious as to why
amrecover "Can't determine disk and mount point from $CWD".
Not that it's too hard to setdisk...but it's strange nonetheless.
Well, you already mentioned one solution: use setdisk. The other one is to
start amrecover
Hi all!
I can't remember if this has been discussed here. At least I didn't find
it in FAQs or archive.
One of my linux clients started issuing this error in the mail 2 days ago:
lithium /usr/wissrech23/schweitz lev 0 FAILED [no backup size line]
[...]
/-- lithium /usr/wissrech23/schweitz lev 0
On Mon, 23 Oct 2000, John R. Jackson wrote:
I'm familiar with the amanda user needing to be in the group
allowed to read raw devices when using 'dump'. Is this also
suffient when using 'tar' or do the file and directory permissions
prevail?
Amanda runs tar underneath a setuid-root
