-\subsection*{Autochanger Resource}
-\index[sd]{Autochanger Resource }
-\index[sd]{Resource!Autochanger }
-\addcontentsline{toc}{subsection}{Autochanger Resource}
-
-The Autochanger resource supports single or multiple drive
-autochangers by grouping one or more Device resources
-into one unit called an autochanger in Bacula (often referred to
-as a "tape library" by autochanger manufacturers).
-
-If you have an Autochanger, and you want it to function correctly,
-you {\bf must} have an Autochanger resource in your Storage
-conf file, and your Director's Storage directives that want to
-use an Autochanger {\bf must} refer to the Autochanger resource name.
-In previous versions of Bacula, the Director's Storage directives
-referred directly to Device resources that were autochangers.
-In version 1.38.0 and later, referring directly to Device resources
-will not work for Autochangers.
+\subsection*{La ressource Autochanger}
+\index[sd]{Autochanger Ressource }
+\index[sd]{Ressource!Autochanger }
+\addcontentsline{toc}{subsection}{Autochanger Ressource}
+La ressource Autochanger supporte les librairies \`a un ou plusieurs
+lecteurs en regroupant une ou plusieurs ressources Device en une
+unit\'e nomm\'ee Autochanger dans Bacula (souvent d\'esign\'ee en tant que
+librairie de bandes par les constructeurs). Si vous poss\'edez une
+librairie, et si vous voulez qu'elle fonctionne correctement, vous
+{\bf devez} avoir une ressource Autochanger dans le fichier de
+configuration de votre Storage Daemon, et les directives Storage
+de votre Director {\bf doivent} se r\'ef\'erer au nom de la ressource
+Autochanger si elles sont suppos\'ees utiliser la librairie. Dans les
+versions ant\'erieures \`a 1.38.0, les directives Storage du Director
+se r\'ef\'eraient directement aux ressources Device qui \'etaient des
+librairies. D\'esormais, ce type de r\'ef\'erence directe ne fonctionne
+plus avec les librairies.
+
\begin{description}
\item [Name = \lt{}Autochanger-Name\gt{}]
\index[sd]{Name}
- Specifies the Name of the Autochanger. This name is used in
- the Director's Storage definition to refer to the autochanger.
- This directive is required.
+ Sp\'ecifie le nom de la librairie. Ce nom est utilis\'e dans la
+ la d\'efinition de ressource Storage du Director afin de d\'esigner
+ la librairie. Cette directive est requise.
\item [Device = \lt{}Device-name1, device-name2, ...\gt{}]
- Specifies the names of the Device resource or
- resources that correspond
- to the autochanger drive. If you have a multiple drive
- autochanger, you must specify multiple Device names, each
- one referring to a separate Device resource that contains a the
- Drive Index specification that corresponds to the drive
- number. You may specify multiple device names on
- a single line separated by commas, and/or you may specify
- multiple Device directives.
- This directive is required.
+ Sp\'ecifie le nom de la (ou des) ressource(s) Device associ\'ees \`a la
+ librairie. Si votre librairie contient plusieurs lecteurs, vous
+ devez sp\'ecifier plusieurs noms de ressources Device, chacun d\'esignant
+ une ressource Device distincte qui comporte un
+ Drive Index correspondant au num\'ero de lecteur. Vous pouvez sp\'ecifier
+ plusieurs noms en une seule ligne s\'epar\'es par des virgules ou/et utiliser
+ plusieurs fois la directive Device. Cette directive est requise.
\item [Changer Device = {\it name-string}]
\index[sd]{Changer Device}
- The specified {\bf name-string} gives the system file name of the autochanger
- device name. If specified in this resource, the Changer Device name
- is not needed in the Device resource. If it is specified in the Device
- resource (see above), it will take precedence over one specified in
- the Autochanger resource.
-
+ La cha\^ine {\bf name-string} sp\'ecifi\'ee indique le nom du fichier syst\`eme
+ d\'esignant la librairie. S'il est sp\'ecifi\'e dans cette ressource, ce nom
+ n'est pas requis dans la ressource Device. Le nom \'eventuellement sp\'ecifi\'e
+ dans la ressource Device prend le pas sur celui sp\'ecifi\'e dans la ressource
+ Autochanger.
+
\item [Changer Command = {\it name-string}]
\index[sd]{Changer Command }
- The {\bf name-string} specifies an external program to be called that will
- automatically change volumes as required by {\bf Bacula}. Most frequently,
- you will specify the Bacula supplied {\bf mtx-changer} script as follows.
- If it is specified here, it need not be specified in the Device
- resource. If it is also specified in the Device resource, it will take
- precedence over the one specified in the Autochanger resource.
+ La cha\^ine {\bf name-string} sp\'ecifie un programme externe appel\'e pour
+ changer de volume automatiquement \`a la demande de Bacula. La plupart du
+ temps, vous renseignerez ce champ avec le script fourni {\bf mtx-changer}
+ comme suit. Si cette commande est sp\'ecifi\'ee ici, elle n'a pas besoin de
+ l'\^etre dans la ressource Device. Dans le cas o\`u elle le serait dans les deux
+ ressources, la sp\'ecification de la ressource Device prendrait le pas sur celle
+ de la ressource Autochanger.
\end{description}
-The following is an example of a valid Autochanger resource definition:
+Voici un exemple de d\'efinition de ressource Autochanger valide :
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-Please note that it is important to include the {\bf Autochanger = yes} directive
-in each Device definition that belongs to an Autochanger. A device definition
-should not belong to more than one Autochanger resource. Also, your Device
-directive in the Storage resource of the Director's conf file should have
-the Autochanger's resource name rather than a name of one of the Devices.
+Notez l'importance de la directive {\bf Autochanger = yes} dans chaque d\'efinition
+de p\'eriph\'erique appartenant \`a une librairie. Un p\'eriph\'erique ne devrait pas \^etre
+d\'efini comme appartenant \`a plusieurs librairies. Aussi, votre directive Device
+dans la ressource Storage du Director devrait comporter le nom de la ressource
+Autochanger plut\^ot que le nom de l'un des lecteurs.
-If you have a drive that physically belongs to an Autochanger but you don't want
-to have it automatically used when Bacula references the Autochanger for backups,
-for example, you want to reserve it for restores, you can add the directive:
+Si vous avez un lecteur qui appartient physiquement \`a une librairie mais que
+vous ne souhaitez pas que Bacula puisse l'utiliser automatiquement (par exemple,
+si vous voulez le r\'eserver pour les restaurations) vous pouvez utiliser la
+directive :
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-to the Device resource for that drive. In that case, Bacula will not automatically
-select that drive when accessing the Autochanger. You can, still use the drive
-by referencing it by the Device name directly rather than the Autochanger name. An example
-of such a definition is shown above for the Device DDS-4-3, which will not be
-selected when the name DDS-4-changer is used in a Storage definition, but will
-be used if DDS-4-3 is used.
+\`a la ressource Device de ce lecteur. Dans ce cas, Bacula ne le s\'electionnera pas
+automatiquement en acc\'edant \`a la librairie. Vous pouvez encore utiliser le lecteur en
+le d\'esignant par son nom de ressource device plut\^ot que par celui de la ressource
+Autochanger. Un exemple d'une telle d\'efinition est montr\'e ci-dessus pour le
+lecteur DDS-4-3, qui ne sera pas s\'electionn\'e si le nom DDS-4-changer est utilis\'e
+dans une ressource Storage, mais le sera si DDS-4-3 est utilis\'e.
+
\addcontentsline{toc}{subsection}{Autochangers -- General}
Bacula provides autochanger support for reading and writing tapes. In
-order to work with an autochanger, Bacula requires three things, each of
+order to work with an autochanger, Bacula requires a number of things, each of
which is explained in more detail after this list:
\begin{itemize}
slot number when you label Volumes.
\end{itemize}
-In version 1.37, there is a new \ilink{Autochanger
+In version 1.37 and later, there is a new \ilink{Autochanger
resource}{AutochangerRes} that permits you to group Device resources thus
-creating a multi-drive autochanger. If you have a multi-drive autochanger,
-you must use this new resource. If you have a single drive autochanger,
-it is recommended, but not required.
+creating a multi-drive autochanger. If you have an autochanger,
+you must use this new resource.
Bacula uses its own {\bf mtx-changer} script to interface with a program
that actually does the tape changing. Thus in principle, {\bf mtx-changer}
LabelMedia = no;
AutomaticMount = yes;
AlwaysOpen = yes;
- Mount Anonymous Volumes = no;
}
\end{verbatim}
\normalsize
LabelMedia = no;
AutomaticMount = yes;
AlwaysOpen = yes;
- Mount Anonymous Volumes = no;
}
Device {
LabelMedia = no;
AutomaticMount = yes;
AlwaysOpen = yes;
- Mount Anonymous Volumes = no;
}
\end{verbatim}
and will not be mounted.
\label{Magazines}
-
\subsection*{Dealing with Multiple Magazines}
\index[general]{Dealing with Multiple Magazines }
\index[general]{Magazines!Dealing with Multiple }
\footnotesize
\begin{verbatim}
+unmount
+(remove magazine)
+(insert new magazine)
update slots
+mount
\end{verbatim}
\normalsize
\begin{enumerate}
\item You can manually set the Slot and InChanger flag using the {\bf update
volume} command in the Console (quite painful).
+
\item You can issue a
- \footnotesize
+\footnotesize
\begin{verbatim}
update slots scan
\end{verbatim}
the magazine in turn and update the information (Slot, InChanger flag) in the
catalog. This is quite effective but does take time to load each cartridge
into the drive in turn and read the Volume label.
+
\item You can modify the mtx-changer script so that it simulates an
autochanger with barcodes. See below for more details.
- \end{enumerate}
+\end{enumerate}
\label{simulating}
-
\subsection*{Simulating Barcodes in your Autochanger}
\index[general]{Autochanger!Simulating Barcodes in your }
\index[general]{Simulating Barcodes in your Autochanger }
\begin{description}
\item [Make sure Bacula is not running.]
- \index[sd]{Make sure Bacula is not running. }
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ list \ 0 \ /dev/nst0 \ 0]
- \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ list \ 0 \ /dev/nst0 \ 0
- }
+\index[sd]{mtx-changer list}
+
This command should print:
\footnotesize
autochanger SCSI control device is generally {\bf /dev/pass2}.
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ slots \ 0 \ /dev/nst0 \ 0]
- \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ slots \ 0 \ /dev/nst0 \ 0
- }
+\index[sd]{mtx-changer slots}
+
This command should return the number of slots in your autochanger.
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ unload \ ]
- \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ unload \ }
+\index[sd]{mtx-changer unload}
+
If a tape is loaded, this should cause it to be unloaded.
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ load \ 3 \ /dev/nst0 \ 0 ]
- \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ load \ 3 \ /dev/nst0 \ 0
- }
+\index[sd]{mtx-changer load}
+
Assuming you have a tape in slot 3, it will be loaded into the read slot (0).
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ loaded \ 0 \ /dev/nst0 \ 0]
- \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ loaded \ 0 \ /dev/nst0 \
- 0 }
+\index[sd]{mtx-changer loaded}
+
It should print "3"
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ unload]
- \index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ unload }
- \end{description}
+\end{description}
Once all the above commands work correctly, assuming that you have the right
{\bf Changer Command} in your configuration, Bacula should be able to operate
%%
%%
-\section*{Console Configuration}
+\section*{Configuration de la Console}
\label{_ChapterStart36}
\index[general]{Configuration!Console}
-\index[general]{Console Configuration}
-\addcontentsline{toc}{section}{Console Configuration}
+\index[general]{Configuration de la Console}
+\addcontentsline{toc}{section}{Configuration de la Console}
\subsection*{General}
\index[general]{General}
\addcontentsline{toc}{subsection}{General}
-The Console configuration file is the simplest of all the configuration files,
-and in general, you should not need to change it except for the password. It
-simply contains the information necessary to contact the Director or
-Directors.
+Le fichier de configuration de la console est le plus siple de tous, et en g\'en\'eral,
+vous n'aurez rien d'autre \`a changer que le mot de passe. Il contient simplement les
+informations n\'ecessaires pour se connecter au(x) Director(s).
-For a general discussion of configuration file and resources including the
-data types recognized by {\bf Bacula}, please see the
-\ilink{Configuration}{_ChapterStart16} chapter of this manual.
-
-The following Console Resource definition must be defined:
-
-\begin{itemize}
-\item
- \ilink{Director}{DirectorResource3} -- to define the
- Director's name and his access password. Note, you may define more than one
-Director resource in the Console configuration file. If you do so, the
-Console program will ask you which one you want to use.
-\end{itemize}
+Pour une discussion g\'en\'erale sur les fichiers de configuration, les ressources et
+les types de donn\'ees reconnus par {\bf Bacula}, consultez le chapitre
+\ilink{Configuration}{_ChapterStart16} de ce manuel.
+
+Les ressources Console suivantes doivent \^etre d\'efinies :
-\subsection*{The Director Resource}
+\subsection*{La ressource Director}
\label{DirectorResource3}
-\index[general]{Director Resource}
-\index[general]{Resource!Director}
-\addcontentsline{toc}{subsection}{Director Resource}
+\index[general]{Director Ressource}
+\index[general]{Ressource!Director}
+\addcontentsline{toc}{subsection}{La ressource Director}
-The Director resource defines the attributes of the Director running on the
-network. You may have multiple Director resource specifications in a single
-Console configuration file. If you have more than one, you will be prompted to
-choose one when you start the {\bf Console} program.
+La ressource Director d\'efinit les attributs du Director ex\'ecut\'e sur le r\'eseau.
+Vous pouvez avoir plusieurs ressources Director dans un seul fichier de
+configuration de console. Dans ce cas, le programme Console vous demandera
+de choisir \`a son lancement le Director vous voulez contacter.
\begin{description}
\item [Director]
\index[console]{Director}
- Start of the Director records.
+ D\'ebut des enregistrements du Director.
\item [Name = \lt{}name\gt{}]
\index[console]{Name}
- The director name used to select among different Directors, otherwise, this
-name is not used.
-
+ Le nom du Director utilis\'e pour choisir entre les diff\'erents Directors.
+ (ce nom n'est utilis\'e que pour {\c c}a).
+
\item [DIRPort = \lt{}port-number\gt{}]
\index[dir]{DIRPort}
- Specify the port to use to connect to the Director. This value will most
-likely already be set to the value you specified on the {\bf
-\verb:--:with-base-port} option of the {\bf ./configure} command. This port must be
-identical to the {\bf DIRport} specified in the {\bf Director} resource of
-the
-\ilink{Director's configuration}{_ChapterStart40} file. The
-default is 9101 so this record is not normally specified.
-
+ Sp\'ecifie le num\'ero de port \`a utiliser pour contacter le Director. cette valeur
+ sera fort probablement d\'ej\`a \'egale \`a celle que vous avez sp\'ecifi\'ee pour
+ l'option {\bf \verb:--:with-base-port} de la commande {\bf configure}. Ce
+ port doit \^etre identique \`a celui sp\'ecifi\'e par la directive {\bf DIRport} de la
+ ressource {\bf Director} du fichier de \ilink{configuration du Director}{_ChapterStart40}.
+ La valeur par d\'efaut est 9101, aussi cet directive n'est normalement pas
+ sp\'ecifi\'ee.
+
\item [Address = \lt{}address\gt{}]
\index[dir]{Address}
- Where the address is a host name, a fully qualified domain name, or a network
-address used to connect to the Director.
+ O\`u "adress" est un nom d'h\^ote, un nom de domaine pleinement qualifi\'e, ou une
+ adresse r\'eseau utlis\'ee pour se connecter au Director.
\item [Password = \lt{}password\gt{}]
\index[dir]{Password}
- Where the password is the password needed for the Director to accept the
-Console connection. This password must be identical to the {\bf Password}
-specified in the {\bf Director} resource of the
-\ilink{Director's configuration}{_ChapterStart40} file. This
-record is required.
+ Ce mot de passe est celui exig\'e par le Director pour accepter la connexion
+ d'une console. Il doit \^etre identique \`a celui sp\'ecifi\'e dans la ressource Director
+ du fichier de \ilink{configuration du Director}{_ChapterStart40}. Cette directive
+ est requise.
+
\end{description}
-An actual example might be:
+Voici un exemple r\'eel :
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-\subsection*{The ConsoleFont Resource}
-\index[general]{Resource!ConsoleFont}
-\index[general]{ConsoleFont Resource}
-\addcontentsline{toc}{subsection}{ConsoleFont Resource}
+\subsection*{La ressource ConsoleFont}
+\index[general]{Ressource!ConsoleFont}
+\index[general]{Ressource ConsoleFont}
+\addcontentsline{toc}{subsection}{Ressource ConsoleFont}
-The ConsoleFont resource is available only in the GNOME version of the
-console. It permits you to define the font that you want used to display in
-the main listing window.
+Cette ressource n'est disponible que dans la version GNOME de la console.
+Elle vous permet de d\'efinir les fontes que vous voulez utiliser pour
+l'affichage dans la fen\^etre principale.
\begin{description}
\item [ConsoleFont]
\index[console]{ConsoleFont}
- Start of the ConsoleFont records.
+ D\'ebut de la ressource ConsoleFont.
\item [Name = \lt{}name\gt{}]
\index[console]{Name}
- The name of the font.
+ Le nom de la fonte.
\item [Font = \lt{}Pango Font Name\gt{}]
\index[console]{Font}
- The string value given here defines the desired font. It is specified in the
-Pango format. For example, the default specification is:
+ La cha\^ine sp\'ecifi\'ee ici d\'efinit la fonte d\'esir\'ee. Elle est sp\'ecifi\'ee au
+ format Pango. Par exemple, la sp\'ecification par d\'efaut est :
\footnotesize
\begin{verbatim}
\end{description}
-Thanks to Phil Stracchino for providing the code for this feature.
+Merci \`a Phil Stracchino d'avoir fourni le code pour cette fonctionnalit\'e.
-An different example might be:
+Un autre exemple :
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-\subsection*{The Console Resource}
+\subsection*{La ressource Console}
\label{ConsoleResource}
-\index[general]{Console Resource}
-\index[general]{Resource!Console}
-\addcontentsline{toc}{subsection}{Console Resource}
+\index[general]{ressource Console}
+\index[general]{Ressource!Console}
+\addcontentsline{toc}{subsection}{Ressource Console}
-As of Bacula version 1.33 and higher, there are three different kinds of
-consoles, which the administrator or user can use to interact with the
-Director. These three kinds of consoles comprise three different security
-levels.
+Depuis la version 1.33 de Bacula, il existe trois types de consoles
+diff\'erents avec lesquels l'administrateur ou l'utilisateur peut
+interagir avec le Director. Ces trois types de consoles comportent
+trois niveaux de s\'ecurit\'e.
\begin{itemize}
-\item The first console type is an {\bf anonymous} or {\bf default} console,
- which has full privileges. There is no console resource necessary for this
- type since the password is specified in the Director resource. This is the
-kind of console that was initially implemented in versions prior to 1.33 and
-remains valid. Typically you would use it only for administrators.
-\item The second type of console, and new to version 1.33 and higher is a
- "named" console defined within a Console resource in both the Director's
- configuration file and in the Console's configuration file. Both the names
-and the passwords in these two entries must match much as is the case for
-Client programs.
-
-This second type of console begins with absolutely no privileges except those
-explicitly specified in the Director's Console resource. Thus you can have
-multiple Consoles with different names and passwords, sort of like multiple
-users, each with different privileges. As a default, these consoles can do
-absolutely nothing -- no commands what so ever. You give them privileges or
-rather access to commands and resources by specifying access control lists in
-the Director's Console resource. Note, if you are specifying such a console,
-you will want to put a null password in the Director resource.
-\item The third type of console is similar to the above mentioned one in that
- it requires a Console resource definition in both the Director and the
- Console. In addition, if the console name, provided on the {\bf Name =}
-directive, is the same as a Client name, the user of that console is
-permitted to use the {\bf SetIP} command to change the Address directive in
-the Director's client resource to the IP address of the Console. This permits
-portables or other machines using DHCP (non-fixed IP addresses) to
-"notify" the Director of their current IP address.
+\item Le premier type de console est la console {\bf anonyme} ou
+ {\bf par d\'efaut}, qui poss\`ede les pleins pouvoirs. Aucune ressource console
+ n'est requise pour ce premier type puisque le mot de passe est sp\'ecifi\'e dans
+ la ressource Director. Ce type de console est le premier \`a avoir \'et\'e
+ impl\'ement\'e, et demeure fonctionnel. Vous le r\'eserverez, typiquement, \`a
+ l'usage exclusif des administrateurs.
+
+\item Le second type, apparu avec la version 1.33, est une console "nomm\'ee"
+ d\'efinie dans des ressources Console dans les fichiers de configuration du
+ Director et dans celui de la console. Les noms et mot de passe dans ces
+ deux fichiers doivent correspondre, comme c'est le cas pour les programmes
+ clients.
+
+ Ce second type de console ne poss\`ede, par d\'efaut, aucun privil\`ege. Pour lui
+ en accorder, vous devez les sp\'ecifier explicitement dans le ressource
+ Console du Director. Ainsi, vous pouvez avoir plusieurs consoles avec des
+ noms et mots de passe distincts et avec, pour chacune, des privil\`eges
+ diff\'erents. Ces consoles ne peuvent, par d\'efaut, absolument rien faire.
+ C'est vous qui leur accordez des privil\`eges ou plut\^ot l'acc\`es \`a des
+ commandes et ressources en sp\'ecifiant des listes de contr\^ole d'acc\`es
+ dans la ressource Console du Director. Notez que si vous sp\'ecifiez une telle
+ console, vous voudrez probablement mettre un mot de passe nul dans la
+ ressource Director.
+
+\item Le troisi\`eme type de console ressemble au pr\'ec\'edent en ce qu'il requiert
+ une d\'efinition de ressource Console dans le fichier de configuration du
+ Director et dans celui de la console. Mais cette console permet aussi, si
+ le nom de la console (la directive {\bf name}) est le m\^eme que celui du client,
+ d'utiliser la commande {\bf SetIP} pour changer la valeur de la directive
+ {\bf Address} dans la ressource client du Director en l'adresse de la console.
+ Ceci permet aux portables et autres machines utilisant DHCP (adresses IP
+ dynamiques) de notifier au Director leur adresse IP courante.
+
\end{itemize}
-The Console resource is optional and need not be specified. However, if it is
-specified, you can use ACLs (Access Control Lists) in the Director's
-configuration file to restrict the particular console (or user) to see only
-information pertaining to his jobs or client machine.
+La ressource Console est optionnelle. Cependant, si elle est sp\'ecifi\'ee,
+vous pouvez utiliser les ACLs (listes de contr\^ole d'acc\`es) dans le fichier
+de configuration du Director pour restreindre une console particuli\`ere
+ou un utilisateur pour qu'ils ne voient que les informations relatives
+\`a ses jobs ou \`a sa machine cliente.
-The following configuration files were supplied by Phil Stracchino. For
-example, if we define the following in the user's bconsole.conf file (or
-perhaps the wx-console.conf file):
+L'exemple ci-dessous nous a \'et\'e fournit par Phil Stracchino. Si nous
+d\'efinissons ce qui suit dans le fichier bconsole.conf (ou wx-console.conf)
+d'un utilisateur :
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-Where the Password in the Director section is deliberately incorrect, and the
-Console resource is given a name, in this case {\bf restricted-client}. Then
-in the Director's bacula-dir.conf file (not directly accessible by the user),
-we define:
+O\`u le mot de passe dans la section Director est d\'elib\'er\'ement incorrect, et
+la console a re{\c c}u le nom {\bf restricted-client}. Si d'autre part, dans le
+fichier de configuration du Director (inaccessible diectement \`a l'utilisateur),
+nous d\'efinissons :
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-the user logging into the Director from his Console will get logged in as {\bf
-restricted-client}, and he will only be able to see or access a Job with the
-name {\bf Restricted Client Save} a Client with the name {\bf
-restricted-client}, a Storage device {\bf main-storage}, any Schedule or Pool,
-a FileSet named {\bf Restricted Client's File}, a Catalog named {\bf
-DefaultCatalog}, and the only command he can use in the Console is the {\bf
-run} command. In other words, this user is rather limited in what he can see
-and do with Bacula.
-
-\subsection*{Console Commands}
-\index[general]{Console Commands}
-\index[general]{Commands!Console}
-\addcontentsline{toc}{subsection}{Console Commands}
-
-For more details on running the console and its commands, please see the
-\ilink{Bacula Console}{_ConsoleChapter} chapter of this manual.
-
-\subsection*{Sample Console Configuration File}
+Alors, l'utilisateur de connectant au Director depuis cette console sera
+connect\'e en tant que {\bf restricted-client}, et il ne sera en mesure
+que de voir ou acc\'eder au job nomm\'e {\bf Restricted Client Save}, avec
+le stockage {\bf main-storage}, n'importe quel planification ou pool, un
+FileSet nomm\'e {\bf Restricted Client's File}, un catalogue nomm\'e
+{\bf DefaultCatalog}, et la seule commande qu'il pourra utiliser dans la console
+sera la commande {\bf run}. En d'autre termes, cet utilisateur est plut\^ot limit\'e
+dans ce qu'il peut voir ou faire avec Bacula.
+
+\subsection*{Commandes de la Console}
+\index[general]{Commandes Console}
+\index[general]{Commandes!Console}
+\addcontentsline{toc}{subsection}{Commandes de la Console}
+
+Pour plus de d\'etails concernant la console et ses commandes, consultez le
+chapitre \ilink{La console Bacula}{_ConsoleChapter} de ce manuel.
+
+\subsection*{Un exemple de fichier de configuration de console}
\label{SampleConfiguration2}
-\index[general]{File!Sample Console Configuration}
-\index[general]{Sample Console Configuration File}
-\addcontentsline{toc}{subsection}{Sample Console Configuration File}
+\index[general]{Fichier!exemple Console Configuration}
+\index[general]{Exemple Console Configuration Fichier}
+\addcontentsline{toc}{subsection}{Exemple Fichier Configuration Console}
-An example Console configuration file might be the following:
+Voici un exemple de fichier de configuration de console :
\footnotesize
\begin{verbatim}
projects / bacula / docs / commitdiff