On Friday 29 September 2006 23:19, Michael Brennen wrote: > > I just logged into Bacula from a client machine that has tighly restricted > access. It can only access its own pools, jobs, etc. > > When I logged in with wx-console I was surprised by a sudden flood of queued > console messages for all jobs from last night. Those messages of course give > quite a bit of detail that I do not want to be seen by the typical client. > > Offhand I don't see a good way in the Console resource to restrict message > access. Is the best option for the moment simply to disable console message > support and depend on email and the logs?
I just looked at the code, and this problem is very likely *much* easier to solve than I thought, in fact, I would classify it as a "bug" since to receive messages, the restricted console should have a "messages" ACL, and if it does not, it should not receive any messages. This will be fixed shortly. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
