On Tue, 30 Jan 2007 16:46:29 +0100, Kern Sibbald wrote > > This is what I would call a bug or more correctly just an oversight. > There are probably a good number of such "little" oversights, many > of which I corrected in version 2.0.0. > > I recommend that you submit a bug report with bugs.bacula.org, which > will ensure that this item is fixed as soon as possible and will not > be lost. >
Thank you for the answer. I submited the report. The following issue can be included in the same category? I'm creating a restricted console with, let's say, settings Set_A. I'm checking from remote console - it's working well. I'm changing the settings for the restricted console to Set_B. I'm reloading the directory configuration file. I'm checking the restricted console - it still have access conform with settings Set_A. I'm restarting the remote console (wx-console) - the restricted console has access conform with settings Set_B. It's not supposed to have the new policy in place just after reloading the directory config file? Restarting bacula-dir determine the remote console to loose the connection with the director, but this is not always an option because any running job will die. Daniel ------------------------------------------------------------------------- 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
