From 43904b4ba81f004e23b64698d936e88dc8bb8cd7 Mon Sep 17 00:00:00 2001 From: Thomas Glatthor Date: Wed, 7 Nov 2007 13:47:02 +0000 Subject: [PATCH] "client" must be "user" and some other corrections --- docs/manual/consoleconf.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manual/consoleconf.tex b/docs/manual/consoleconf.tex index c564f955..563c81ad 100644 --- a/docs/manual/consoleconf.tex +++ b/docs/manual/consoleconf.tex @@ -242,7 +242,7 @@ Console { \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 +Console resource is given a name, in this case {\bf restricted-user}. Then in the Director's bacula-dir.conf file (not directly accessible by the user), we define: @@ -264,10 +264,10 @@ Console { \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 +restricted-user}, 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 +a FileSet named {\bf Restricted Client's FileSet}, 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. -- 2.39.5