fix for #693333, hard-coding of amandabackup as user in many scripts and docs

[debian/amanda] / man / xml-source / amsuntar.8.xml

diff --git a/man/xml-source/amsuntar.8.xml b/man/xml-source/amsuntar.8.xml
index f29a93103ec55bb8c82353f4c3454792c5b62cb0..f11afc52dec531467ec2c62d4b740c112a4988dc 100644 (file)
--- a/man/xml-source/amsuntar.8.xml
+++ b/man/xml-source/amsuntar.8.xml
@@ -34,11 +34,14 @@ by users directly. It uses Solaris bundled tar utility to backup and
 restore data. Currenty ACLs from ZFS file system can only be backed up
 using the solaris supplied tar utility.</para>
 
+<para>The <emphasis remap='B'>diskdevice</emphasis> in the disklist (DLE)
+must be the directory to backup.</para>
+
 <para>Solaris 10 supports Role Based Access Control(RBAC) which is enabled
 by default. To run backup operations using  sun tar utility by under 
-privileged user like amandabackup, amandabackup user need to have proper 
+privileged user like backup, backup user need to have proper 
 roles and profiles, specially "Media Backup" profile/role. This can be done 
-using 'usermod -P "Media Backup" amandabackup' command.</para>
+using 'usermod -P "Media Backup" backup' command.</para>
 
 
 </refsect1>
@@ -71,6 +74,11 @@ Include extended attributes in archive.  The default is YES.
 Write tar file with extended headers. With this optiion the modification time
 is maintained with a  granularity of microseconds,Long file names and file 
 sizes greater than 8GB can be archived. The default is YES.
+</listitem></varlistentry>
+
+ <!-- ==== -->
+ <varlistentry><term>SUNTAR-PATH</term><listitem>
+The path to the suntar binary. The default is set when Amanda is built.
 </listitem></varlistentry>
 
  <!-- ==== -->