So it appears that restricted consoles are automatically put in the default
catalog.  Nicely however, "use" is smart to where the client belongs:

*use
Automatically selected Catalog: clientsCatalog
Using Catalog name=clientsCatalog DB=bacula_clients
*

So I guess two things are necessary:

1. Make the default catalog be the catalog where most restricted consoles
would be.

2. Write a patch to make sure that restricted clients have access to the
default catalog before putting them there?
        -or perhaps easier-
   automatically issue a "use" command on entry?

On Sat, Aug 19, 2006 at 10:11:53AM -0700, Jo Rhett wrote:
> So I did some testing using the examples from the documentation and came up
> with this test of my personal machine:
> 
> Console {
>         Name = triceratops.lizardarts.com-console
>         Password = "*removed*"
>         JobACL = "triceratops.lizardarts.com"
>         ClientACL = triceratops.lizardarts.com-fd
>         StorageACL = Disk_clients
>         ScheduleACL = *all*
>         PoolACL = clients_Pool
>         FileSetACL = *all*
>         CatalogACL = clientsCatalog
>         CommandACL = restore
> }
 
-- 
Jo Rhett
senior geek
SVcolo : Silicon Valley Colocation

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to