file works

docs/manuals/en/new_main_reference/replace.sh

@@ -89,6 +89,9 @@ sed -i -E 's|:raw-latex:`\\sinceVersion\{(.*)\}\{(.*)\}\{(.*)\}`|\3|g' *.rst
 #sed -i -E 's#:raw-latex:`\\sinceVersion\{(.*)\}\{(.*)\}\{(.*)\}`#\n\n.. versionadded:: \3\n   \1 \2\n#g' *.rst
 
 
+# file
+sed -i -E 's|:raw-latex:`\\file\{(.*)\}`|:file:`\1`|g' *.rst
+
 
 
 

docs/manuals/en/new_main_reference/source/autochangers.rst

@@ -21,7 +21,7 @@ each of which is explained in more detail after this list:
    sent by Bareos. Bareos contains the script
    :program:`mtx-changer`, that utilize the command
    :program:`mtx`. It’s config file is normally located at
-   :raw-latex:`\file{/etc/bareos/mtx-changer.conf}`
+   :file:`/etc/bareos/mtx-changer.conf`
 
 -  That each Volume (tape) to be used must be defined in the Catalog and
    have a Slot number assigned to it so that Bareos knows where the
@@ -179,8 +179,8 @@ device.
 
 The following tip for FreeBSD users comes from Danny Butroyd: on reboot
 Bareos will NOT have permission to control the device
-:raw-latex:`\file{/dev/pass0}` (assuming this is your changer device).
-To get around this just edit the :raw-latex:`\file{/etc/devfs.conf}`
+:file:`/dev/pass0` (assuming this is your changer device).
+To get around this just edit the :file:`/etc/devfs.conf`
 file and add the following to the bottom: :raw-latex:`\footnotesize`
 
 ::
@@ -211,7 +211,7 @@ Solaris
 ~~~~~~~
 
 On Solaris, the changer device will typically be some file under
-:raw-latex:`\file{/dev/rdsk}`.
+:file:`/dev/rdsk`.
 
 Slots
 -----
@@ -1097,7 +1097,7 @@ This shows that the block size for the data blocks that we need is
 131072.
 
 Now we have to set this block size in the
-:raw-latex:`\file{bareos-sd.conf}`, device resource as
+:file:`bareos-sd.conf`, device resource as
 :raw-latex:`\linkResourceDirective{Sd}{Device}{Maximum Block Size}`:
 
 ::

docs/manuals/en/new_main_reference/source/bconsole.rst

@@ -686,7 +686,7 @@ configure
 
               \file{/etc/bareos/bareos-dir.d/client/client2-fd.conf}
 
-        -  :raw-latex:`\file{/etc/bareos/bareos-dir-export/client/client2-fd/bareos-fd.d/director/bareos-dir.conf}`
+        -  :file:`/etc/bareos/bareos-dir-export/client/client2-fd/bareos-fd.d/director/bareos-dir.conf`
            (assuming your director resource is named
            :raw-latex:`\name{bareos-dir}`)
 
@@ -1201,7 +1201,7 @@ list
 
     If you wish to add specialized commands that list the contents of
     the catalog, you can do so by adding them to the
-    :raw-latex:`\file{query.sql}` file. However, this takes some
+    :file:`query.sql` file. However, this takes some
     knowledge of programming SQL. Please see the
     :raw-latex:`\bcommand{query}{}` command below for additional
     information. See below for listing the full contents of a catalog

docs/manuals/en/new_main_reference/source/catmaintenance.rst

@@ -70,10 +70,10 @@ The **dbconfig-common** configuration (and
 credentials) is done by the
 **bareos-database-common** package. Settings are
 stored in the file
-:raw-latex:`\file{/etc/dbconfig-common/bareos-database-common.conf}`.
+:file:`/etc/dbconfig-common/bareos-database-common.conf`.
 
 The Bareos database backend will get automatically configured in
-:raw-latex:`\file{/etc/bareos/bareos-dir.d/catalog/MyCatalog.conf}`. If
+:file:`/etc/bareos/bareos-dir.d/catalog/MyCatalog.conf`. If
 the Server is not running locally you need to specify
 :raw-latex:`\linkResourceDirective{Dir}{Catalog}{DB Address}` in the
 catalog ressource. A later reconfiguration might require manual adapt
@@ -476,7 +476,7 @@ with the credentials of the database administrator:
     password=<input>YourPasswordForAccessingMysqlAsRoot</input>
 
 Alternatively you can specifiy your database password by adding it to
-the file :raw-latex:`\file{/etc/my.cnf}`.
+the file :file:`/etc/my.cnf`.
 
 Verify that you have specified the correct settings by calling the
 :program:`mysql` command. If this connects you to the
@@ -710,7 +710,7 @@ supported. Because its setup is easy, it is a good database for testing.
 However please don’t use it in a production environment.
 
 Sqlite stores a database in a single file. Bareos creates this file at
-:raw-latex:`\file{/var/lib/bareos/bareos.db}`.
+:file:`/var/lib/bareos/bareos.db`.
 
 Sqlite does not offer access permissions. The only permissions that do
 apply are the Unix file permissions.
@@ -1025,7 +1025,7 @@ from scratch producing a compacted result, so below, we show you how you
 can do this for PostgreSQL.
 
 For a PostgreSQL database, you could write the Bareos database as an
-ASCII file (:raw-latex:`\file{bareos.sql}`) then reload it by doing the
+ASCII file (:file:`bareos.sql`) then reload it by doing the
 following:
 
 ::

docs/manuals/en/new_main_reference/source/configure.rst

@@ -476,7 +476,7 @@ Including other Configuration Files
 If you wish to break your configuration file into smaller pieces, you
 can do so by including other files using the syntax
 :raw-latex:`\configdirective{@filename}` where
-:raw-latex:`\file{filename}` is the full path and filename of another
+:file:`filename` is the full path and filename of another
 file. The :raw-latex:`\configdirective{@filename}` specification can be
 given anywhere a primitive token would appear.
 
@@ -558,7 +558,7 @@ easier human recognition. For example:
 
 defines the Director resource with the name
 :raw-latex:`\parameter{bareos-dir}` and a query file
-:raw-latex:`\file{/usr/lib/bareos/scripts/query.sql}`.
+:file:`/usr/lib/bareos/scripts/query.sql`.
 
 .. index::
    pair: Configuration; Naming Convention
@@ -961,7 +961,7 @@ net-addresses
     address can be specified as either a dotted quadruple, or in IPv6
     colon notation, or as a symbolic name (only in the ip
     specification). Also, the port can be specified as a number or as
-    the mnemonic value from the :raw-latex:`\file{/etc/services}` file.
+    the mnemonic value from the :file:`/etc/services` file.
     If a port is not specified, the default one will be used. If an ip
     section is specified, the resolution can be made either by IPv4 or
     IPv6. If ip4 is specified, then only IPv4 resolutions will be
@@ -1441,7 +1441,7 @@ files, you will need to take care to keep them consistent.
 
 In the left column, you can see the Director, Storage, and Client
 resources and their corresponding names and passwords – these are all in
-:raw-latex:`\file{bareos-dir.conf}`. In the right column the
+:file:`bareos-dir.conf`. In the right column the
 corresponding values in the Console, Storage daemon (SD), and File
 daemon (FD) configuration files are shown.
 

docs/manuals/en/new_main_reference/source/consoleconf.rst

@@ -207,7 +207,7 @@ Using Named Consoles
 The following configuration files were supplied by Phil Stracchino.
 
 To use named consoles from :program:`bconsole`, use a
-:raw-latex:`\file{bconsole.conf}` configuration file like this:
+:file:`bconsole.conf` configuration file like this:
 
 ::
 
@@ -259,7 +259,7 @@ the only command he can use in the Console is the
 rather limited in what he can see and do with Bareos. For details how to
 configure ACLs, see the :raw-latex:`\dt{Acl}` data type description.
 
-The following is an example of a :raw-latex:`\file{bconsole.conf}` file
+The following is an example of a :file:`bconsole.conf` file
 that can access several Directors and has different Consoles depending
 on the Director:
 

docs/manuals/en/new_main_reference/source/critical.rst

@@ -58,7 +58,7 @@ are in production, use the checklist anyway).
    :raw-latex:`\linkResourceDirective{Dir}{Job}{Write Bootstrap}`
    directive and more details are available in the
    :ref:`BootstrapChapter` chapter. Also, the default
-   :raw-latex:`\file{bareos-dir.conf}` comes with a Write Bootstrap
+   :file:`bareos-dir.conf` comes with a Write Bootstrap
    directive defined. This allows you to recover the state of your
    system as of the last backup.
 

docs/manuals/en/new_main_reference/source/debug.rst

@@ -112,7 +112,7 @@ debugger. Solaris:raw-latex:`\index[general]{Platform!Solaris!Debug}`
 with :program:`dbx` loaded works quite fine. On other
 systems, you will need to modify the :program:`btraceback`
 program to invoke the correct debugger, and possibly correct the
-:raw-latex:`\file{btraceback.gdb}` script to have appropriate commands
+:file:`btraceback.gdb` script to have appropriate commands
 for your debugger. Please keep in mind that for any debugger to work, it
 will most likely need to run as root.
 

docs/manuals/en/new_main_reference/source/howto.rst

@@ -820,7 +820,7 @@ section of a File Set, e.g.:
     }
 
 This causes the File Daemon to call bpipe plugin, which will write its
-data into the "pseudo" file :raw-latex:`\file{/POSTGRESQL/dump.sql}` by
+data into the "pseudo" file :file:`/POSTGRESQL/dump.sql` by
 calling the program :program:`pg_dumpall -U postgres` to
 read the data during backup. The :program:`pg_dumpall`
 command outputs all the data for the database, which will be read by the
@@ -923,16 +923,16 @@ As it is a Python plugin, it will also require to have the package
 **bareos-filedaemon-python-plugin** installed on the
 |bareosFd|, where you run it.
 
-For authentication the :raw-latex:`\file{.mycnf}` file of the user
+For authentication the :file:`.mycnf` file of the user
 running the |bareosFd|. Before proceeding, make sure that
 xtrabackup can connect to the database and create backups.
 
 Installation
 ^^^^^^^^^^^^
 
 Make sure you have met the prerequisites. Install the files
-:raw-latex:`\file{BareosFdPercona.py}` and
-:raw-latex:`\file{bareos-fd-percona.py}` in your Bareos plugin directory
+:file:`BareosFdPercona.py` and
+:file:`bareos-fd-percona.py` in your Bareos plugin directory
 (usually :raw-latex:`\directory{/usr/lib64/bareos/plugins}`). These
 files are available in the Git repository
 `https://github.com/bareos/bareos-contrib/tree/master/fd-plugins/bareos_percona <https://github.com/bareos/bareos-contrib/tree/master/fd-plugins/bareos_percona>`_.
@@ -1138,7 +1138,7 @@ mysqluser
 
 mysqlpassword
     MySQL password. Default: unset (better use
-    :raw-latex:`\file{my.cnf}` to store passwords)
+    :file:`my.cnf` to store passwords)
 
 On restore, the database dumps are restored to the subdirectory
 ``path:_mysqlbackups_`` in the restore path. The database restore must

docs/manuals/en/new_main_reference/source/install.rst

@@ -53,8 +53,8 @@ is available at
 `http://download.bareos.org/bareos/release/latest/ <http://download.bareos.org/bareos/release/latest/>`_.
 
 The public key to verify the repository is also in repository directory
-(:raw-latex:`\file{Release.key}` for Debian based distributions,
-:raw-latex:`\file{repodata/repomd.xml.key}` for RPM based
+(:file:`Release.key` for Debian based distributions,
+:file:`repodata/repomd.xml.key` for RPM based
 distributions).
 
 Section :ref:`section-InstallBareosPackages` describes
@@ -416,7 +416,7 @@ Make sure, that :raw-latex:`\user{root}` has direct access to the local
 MySQL server. Check if the command :program:`mysql` connects
 to the database without defining the password. This is the default on
 RedHat and SUSE distributions. On other systems (Debian, Ubuntu), create
-the file :raw-latex:`\file{~/.my.cnf}` with your authentication
+the file :file:`~/.my.cnf` with your authentication
 informations:
 
 ::
@@ -442,7 +442,7 @@ following commands:
     /usr/lib/bareos/scripts/grant_bareos_privileges
 
 As some Bareos updates require a database schema update, therefore the
-file :raw-latex:`\file{/root/.my.cnf}` might also be useful in the
+file :file:`/root/.my.cnf` might also be useful in the
 future.
 
 .. _section-StartDaemons:

docs/manuals/en/new_main_reference/source/ndmp.rst

@@ -440,7 +440,7 @@ Additionally, we need to define the access credentials for our NDMP TAPE
 AGENT (Secondary Storage) inside of this Storage Daemon.
 
 These are configured by adding a NDMP resource to
-:raw-latex:`\file{bareos-sd.conf}`:
+:file:`bareos-sd.conf`:
 
 ::
 
@@ -1078,7 +1078,7 @@ We set up an additional |bareosSd| on a host named
 
 When this is done, add a second storage resource
 :raw-latex:`\resourcename{Dir}{Storage}{File2}` to the
-:raw-latex:`\file{bareos-dir.conf}`:
+:file:`bareos-dir.conf`:
 
 ::
 

docs/manuals/en/new_main_reference/source/passiveclient.rst

@@ -55,7 +55,7 @@ client definition of the |bareosDir|:
 
 Also, prior to bareos version 15, you need to set
 :raw-latex:`\linkResourceDirective{Fd}{Client}{Compatible}`=no in the
-:raw-latex:`\file{bareos-fd.conf}` configuration file. Since Bareos
+:file:`bareos-fd.conf` configuration file. Since Bareos
 Version 15, the compatible option is set to no per default and does not
 need to be specified anymore.
 

docs/manuals/en/new_main_reference/source/programs.rst

@@ -225,7 +225,7 @@ you will then specify the Volume name or Volume names if more than one
 volume is needed. For example, suppose you want to read tapes
 :raw-latex:`\volume{tapevolume1}` and :raw-latex:`\volume{tapevolume2}`.
 First construct a **bootstrap** file named say,
-:raw-latex:`\file{list.bsr}` which contains:
+:file:`list.bsr` which contains:
 
 .. raw:: latex
 
@@ -762,7 +762,7 @@ Extracting Under Windows
 To use :program:`bextract`, the Bareos Storage Daemon must
 be installed. As bextract works on tapes or disk volumes, these must be
 configured in the Storage Daemon configuration file, normally found at
-:raw-latex:`\file{C:\ProgrammData\Bareos\bareos-sd.conf}`. However, it
+:file:`C:\ProgrammData\Bareos\bareos-sd.conf`. However, it
 is not required to start the Bareos Storage Daemon. Normally, if the
 Storage Daemon would be able to run, :program:`bextract`
 would not be required.

docs/manuals/en/new_main_reference/source/rescue.rst

@@ -137,7 +137,7 @@ ReaR is:
     BAREOS_CLIENT=bareosclient-fd
 
 You also need to specify in your ReaR configuration file
-(:raw-latex:`\file{/etc/rear/local.conf}`) where you want to store your
+(:file:`/etc/rear/local.conf`) where you want to store your
 recovery images. Please refer to the
 `ReaR documentation <http://relax-and-recover.org/documentation/>`_
 for details.

docs/manuals/en/new_main_reference/source/supportedoses.rst

@@ -283,7 +283,7 @@ The Bareos installer package for Mac OS X contains the
 On your local Mac, you must be an admin user. The main user is an admin
 user.
 
-Download the :raw-latex:`\file{bareos-client*.pkg}` installer package
+Download the :file:`bareos-client*.pkg` installer package
 from `http://download.bareos.org/bareos/release/latest/MacOS/ <http://download.bareos.org/bareos/release/latest/MacOS/>`_.
 
 Find the .pkg you just downloaded. Install the .pkg by holding the CTRL

docs/manuals/en/new_main_reference/source/troubleshooting.rst

@@ -28,8 +28,8 @@ on a different machine. They are:
    the Director’s machine and the Client’s machine (or on port 9103
    between the Client and the Storage daemon machines).
 
--  If your system is using Tcpwrapper (:raw-latex:`\file{hosts.allow}`
-   or :raw-latex:`\file{hosts.deny}` file), verify that is permitting
+-  If your system is using Tcpwrapper (:file:`hosts.allow`
+   or :file:`hosts.deny` file), verify that is permitting
    access.
 
 -  Your password or names are not correct in both the Director and the
@@ -234,7 +234,7 @@ testing before you put it into production.
 When using random access media as backup space (e.g. disk), you should
 also read the chapter about :ref:`ConcurrentDiskJobs`.
 
-Below is a super stripped down :raw-latex:`\file{bareos-dir.conf}` file
+Below is a super stripped down :file:`bareos-dir.conf` file
 showing you the four places where the the file must be modified to allow
 the same job :raw-latex:`\resourcename{Dir}{Job}{NightlySave}` to run up
 to four times concurrently. The change to the Job resource is not
@@ -508,7 +508,7 @@ command. After the **mtx-changer** script returns, Bareos will
 immediately rewind and read the tape. If Bareos gets rewind I/O errors
 after a tape change, you will probably need to configure the
 :raw-latex:`\parameter{load_sleep}` paramenter in the config file
-:raw-latex:`\file{/etc/bareos/mtx-changer.conf}`. You can test whether
+:file:`/etc/bareos/mtx-changer.conf`. You can test whether
 or not you need a **sleep** by putting the following commands into a
 file and running it as a script:
 
@@ -533,7 +533,7 @@ does not run, start by putting a **sleep 30** or possibly a **sleep 60**
 in the script just after the mtx-changer load command. If that works,
 then you should configure the :raw-latex:`\parameter{load_sleep}`
 paramenter in the config file
-:raw-latex:`\file{/etc/bareos/mtx-changer.conf}` to the specified value
+:file:`/etc/bareos/mtx-changer.conf` to the specified value
 so that it will be effective when Bareos runs.
 
 A second problem that comes up with a small number of autochangers is
@@ -561,7 +561,7 @@ just after the unload so that the script looks like:
 
 If this solves your problems, set the parameter
 :raw-latex:`\parameter{offline}` in the config file
-:raw-latex:`\file{/etc/bareos/mtx-changer.conf}` to "1".
+:file:`/etc/bareos/mtx-changer.conf` to "1".
 
 Restore
 =======