update client and server readme files

[debian/amanda] / debian / amanda-server.README.Debian

diff --git a/debian/amanda-server.README.Debian b/debian/amanda-server.README.Debian
index 6526640ff29d4ea2cf397ace101e7891ef7a9e33..c51849cdb6dc7fa5747aae3c8ffa5b10a500cb68 100644 (file)
--- 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.
 
 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.
 
 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.
 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
 
     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.
 
 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.
 
 >      - use the proposed work-around
 >      - ignore those messages in your logcheck.
 

-
-