Hi

>Hi,
>
>29.07.2008 14:24, Ronald Buder wrote:
>>Hi,
>>
>>we run a rather large (and quickly growing) installation, 46 clients
>>at
>>the moment, the 100 soon to be reached. Being a test center we offer
>>backup services through Bacula to several different projects, each of
>>which has it's own infrastructure. It's quite a bit of typing to
>>create
>>ACLSets for each of the projects, so that they can only see and
>>control
>>the jobs they're associated with.
>
>I would have tried to implement this semi-automatically, i.e. create a
>template for the ACLs and change to the actual user data using sed or
>awk, to create a block of text to insert into the configuration or a
>file to include.

Sounds like a plan, sure. This was mainly a kickoff procedure to get
ACLs going in the first place. VI, a bunch of shell scripts, worked out
pretty good even if it was a bit of work :)

>
>>I successfully created an ACL-Set this
>>morning including 16 clients, dozens of filesets etc. for a single
>>project. Everything works out the way it's supposed to be, they can
>>run
>>jobs, restore files, list clients and jobs and so on. However, they
>>receive all messages the server produces, whether they are assoziated
>>with the project or not.
>>
>>I might just be missing something, so if someone could kindly point me
>>into the right direction. I would like to filter the messages so that
>>the project only receives notifications concerning their clients and
>>jobs and theirs only.
>
>Hmm... I don't think this is supported.
>
>You could always disable messages to the console and manage the
>notifications by mail only.

That's an option, thx. I'll keep that in mind.

>
>In most of the installations I manage that would work, because after
>the initial setup, the console is used seldomly, and I don't think
>restricted users would need to do "global" administrative tasks at
>all. The global admin could easily access the log file.

Not only do we not want them to have the "need" to perform any
administrative tasks on the server, more so we require them not to under
any circumstances. Having untrained users administer a backup server
would be a disaster. Like I said, fairly large at the moment, growing
quickly... .

>
>>Thx for any help in advance...
>
>Well, I don't know if this really helps... alternatively, either
>submit a feature request or create the necessary patch :-)

It helped nonetheless. :)

>
>Arno
>
Ronald



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users