>>>>> On Wed, 17 Oct 2012 17:24:06 +0200, said:
>
> To solve things, I've tried setting ACL's in the Console statement like this:
>
> Console {
> Name = Almond
> Password = ""
> ClientACL = Almond
> StorageACL = Almond_Storage
> PoolACL = Almond_Pool
> }
>
> But this doesn't work. I thought this would limit the client as defined in
> Client { Name= Almond.....} to access only the listed storage and pools
> (which would be great, as almond has it's own reserved pool), but it doesn't
> do that. I think I may be interpreting the manual the wrong way. I've
> googled and found several other people asking the same question, but no
> working answers.
The Console statement in bacula-dir.conf isn't designed to match a named
Client statement. You need to put a special bconsole.conf on the client, so
that it uses the Console directive in the bacula-dir.conf.
See the restricted-user examples here:
http://www.bacula.org/5.2.x-manuals/en/main/main/Console_Configuration.html
__Martin
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
