From 322fc055c22c414a2baf9159b8eb8e74a84f70c7 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Tue, 13 Sep 2011 14:02:26 -0600 Subject: [PATCH] update client and server readme files --- debian/amanda-client.README.Debian | 6 ++---- debian/amanda-server.README.Debian | 5 ----- 2 files changed, 2 insertions(+), 9 deletions(-) diff --git a/debian/amanda-client.README.Debian b/debian/amanda-client.README.Debian index 5390888..30b4c02 100644 --- a/debian/amanda-client.README.Debian +++ b/debian/amanda-client.README.Debian @@ -1,16 +1,14 @@ Notes on making amanda-client work on a Debian system - To get indexing (or specifically amrecover) to work right two things need to be done: -1. Edit server's /etc/hosts.allow and allow all client machines into - the daemons amindexd & amidxtaped. +1. If you're using tcpd, make sure to edit the server's /etc/hosts.allow and + allow all client machines into the daemon amandad 2. Edit the server(s) ~backup/.amandahosts and add an entry like: " root" - As always: for more complex setups consult the manpages and available documentation in /usr/share/doc/amanda-common ;-) diff --git a/debian/amanda-server.README.Debian b/debian/amanda-server.README.Debian index 6526640..c51849c 100644 --- a/debian/amanda-server.README.Debian +++ b/debian/amanda-server.README.Debian @@ -47,12 +47,10 @@ machine. On Debian systems, this is usually linked to /etc/amandahosts, but if you have clients running other operating systems you'll have to find the right place yourself. - NOTE: If you want to backup your server too, you need to treat it as both a client *and* a server, see /usr/share/doc/amanda-client/README.Debian for more information. - For more complex setups, consult the manpages and the extra documents and example files in /usr/share/doc/amanda-common, or look at www.amanda.org on the web. @@ -72,7 +70,6 @@ his experience using ftape: pre-install zftape /sbin/swapout 5 post-install zftape /bin/ftmt -f /dev/nzqft0 setblk 32768 - To ease use with firewalls, Amanda has been built with options restricting the use of TCP to the port range 50000-50100, and UDP to the port range 840-860. @@ -145,5 +142,3 @@ This information from Marc Schaefer may relevant: > - use the proposed work-around > - ignore those messages in your logcheck. - - -- 2.30.2