On Tuesday 25 May 2010 15:13:36 Anatoly Pugachev wrote: > On 04.05.2010 / 13:33:12 -0400, Morty Abzug wrote: > > However, format/architectural issues are indeed harder to overcome. > > There are a number of limitations I have encountered with bacula, and > > it looks like at least some of them might be fundamental to bacula's > > architecture. My list: > > > > (12) bconsole should support an option for execute-one-command (i.e. -e) > > how it is different from: > > echo list jobs | bconsole > > but I've tried to implement "-e " command line switch, it takes about 30 > lines of code actually... > > > (13) bconsole should support an option for batch mode (i.e. -b) > > actually bconsole is always reading .bconsolerc file and you can put > commands in it, but it's not a proper usage for a "batch mode". Writting a > patch for batch mode should be no harder than my implementaion of "-e" > command line. If anyone interested for a patch code review, I can push it > to a SF git repository.
I don't think there is any need for either a -e option nor a -b option. Both can easily be done via the shell. Anatoly already pointed out how to send a single command. One way to do a sort of batch mode is: bconsole <<EOF command1 command2 ... EOF There are, of course, many other ways of doing it. Best regards, Kern ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
