From: Kern S. <ke...@si...> - 2014-04-12 08:38:55
|
<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Hello Heath,<br> <br> Thanks for using Bacula.<br> <br> I guess it is not much fun to read such a large manual, so perhaps I could suggest that it is fun to go off to a Bacula Admin I course -- all students love it, and in that course you learn about Bacula without having to read the manual. You also learn that commas between items such as Months and days of the week are perfectly well handled by Bacula. The same is true for ranges of months and days by separating the start and end days with a hyphen.<br> <br> Bottom line: this has been implemented in Bacula from the beginning.<br> <br> By the way, the best place to file a feature request is in the bugs database (features section).<br> <br> Best regards,<br> Kern<br> <br> On 04/12/2014 12:22 AM, Heath Petersen wrote:<br> </div> <blockquote cite="mid:CADcrBrmLfAWx7nFEJc-9=wa0JBZPWwxCZAnt3nbGB=pNq...@ma..." type="cite"> <div dir="ltr"> <div> <div><font face="courier new, monospace">Item 1: Allow combinations of parameters separated by commas</font></div> <div><font face="courier new, monospace"> in job schedules</font></div> <div><font face="courier new, monospace"> Date: 11 April 2014</font></div> <div><font face="courier new, monospace"> Origin: Heath Petersen <a class="moz-txt-link-rfc2396E" href="mailto:Heath@HPetersenFamily.com"><Heath@HPetersenFamily.com></a> </font></div> <div><font face="courier new, monospace"> Status: </font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> What: The ability to allow combinations of parameters</font></div> <div><font face="courier new, monospace"> separated by commas would clean up some schedule</font></div> <div><font face="courier new, monospace"> definitions. </font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> Why: An example is the easiest way to explain this -</font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> Schedule {</font></div> <div><font face="courier new, monospace"> Name = "dailyWithFullEveryOtherMonth"</font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> Run = Level=Full Jan 1st Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Level=Differential Feb 1st Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Level=Full Mar 1st Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Level=Differential Apr 1st Sun at 23:05</font></div> <div><font face="courier new, monospace"> .</font></div> <div><font face="courier new, monospace"> . Shortened for readability.</font></div> <div><font face="courier new, monospace"> .</font></div> <div><font face="courier new, monospace"> Run = Level=Differential Dec 1st Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Level=Differential 2nd-5th Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Incremental Mon-Sat at 23:05</font></div> <div><font face="courier new, monospace"> }</font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> Could be simplified to -</font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> Schedule {</font></div> <div><font face="courier new, monospace"> Name = "dailyWithFullEveryOtherMonth"</font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> Run = Level=Full Jan,Mar,May,Jul,Sep,Nov 1st Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Level=Differential Feb,Apr,Jun,Aug,Oct,Dec 1st Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Level=Differential 2nd-5th Sun at 23:05</font></div> <div><font face="courier new, monospace"> Run = Incremental Mon-Sat at 23:05</font></div> <div><font face="courier new, monospace"> }</font></div> <div><font face="courier new, monospace"><br> </font></div> <div><font face="courier new, monospace"> Notes: Comma operators could be allowed in the specification of the month,</font></div> <div><font face="courier new, monospace"> weekday, and time. Program logic would have to expand to all combinations.</font></div> <div><font face="courier new, monospace"> Ex: Jan,Feb 1st Sun,Wed would have to expand to Jan 1st Sun, Jan 1st Wed,</font></div> <div><font face="courier new, monospace"> Feb 1st Sun, Feb 1st Wed.</font></div> </div> <div><br> </div> <div><br> </div> ----------<br clear="all"> <div> <div dir="ltr"> <p>Heath Petersen</p> <p>Email: <a class="moz-txt-link-abbreviated" href="mailto:Heath@HPetersenFamily.com">Heath@HPetersenFamily.com</a></p> <p>Cell: 507-220-2485</p> <p><br> </p> <p><img src="cid:par...@si..." alt="American Red Cross" style="font-family: Arial, sans-serif; font-size: 10pt;" width="160" height="54"><br> </p> <p>Health Services Leader</p> <p><a moz-do-not-send="true" href="http://www.redcross.org/mn/worthington" target="_blank">Southwest Minnesota Chapter, Worthington</a></p> <p><br> </p> </div> </div> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. <a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/13600_Cloudbees">http://p.sf.net/sfu/13600_Cloudbees</a></pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Bacula-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Bac...@li...">Bac...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/bacula-devel">https://lists.sourceforge.net/lists/listinfo/bacula-devel</a> </pre> </blockquote> <br> </body> </html> |
From: Heath P. <Heath@HPetersenFamily.com> - 2014-04-12 14:19:22
|
http://www.bacula.org/5.2.x-manuals/en/main/main/Configuring_Director.html#SECTION001450000000000000000 does not mention the comma operator. That is what I was going by. I guess I should have tried it. Thanks for the information and quick reply. Also, http://blog.bacula.org/support/feature-requests/ states to submit feature requests in this manner. I will do it the way you mention in the future. Thank you. Heath Petersen Email: Heath@HPetersenFamily.com Cell: 507-220-2485 Health Services Leader Southwest Minnesota Chapter, Worthington On Sat, Apr 12, 2014 at 3:38 AM, Kern Sibbald <ke...@si...> wrote: > > Hello Heath, > > Thanks for using Bacula. > > I guess it is not much fun to read such a large manual, so perhaps I could suggest that it is fun to go off to a Bacula Admin I course -- all students love it, and in that course you learn about Bacula without having to read the manual. You also learn that commas between items such as Months and days of the week are perfectly well handled by Bacula. The same is true for ranges of months and days by separating the start and end days with a hyphen. > > Bottom line: this has been implemented in Bacula from the beginning. > > By the way, the best place to file a feature request is in the bugs database (features section). > > Best regards, > Kern > > On 04/12/2014 12:22 AM, Heath Petersen wrote: > > Item 1: Allow combinations of parameters separated by commas > in job schedules > Date: 11 April 2014 > Origin: Heath Petersen <Heath@HPetersenFamily.com> > Status: > > What: The ability to allow combinations of parameters > separated by commas would clean up some schedule > definitions. > > Why: An example is the easiest way to explain this - > > Schedule { > Name = "dailyWithFullEveryOtherMonth" > > Run = Level=Full Jan 1st Sun at 23:05 > Run = Level=Differential Feb 1st Sun at 23:05 > Run = Level=Full Mar 1st Sun at 23:05 > Run = Level=Differential Apr 1st Sun at 23:05 > . > . Shortened for readability. > . > Run = Level=Differential Dec 1st Sun at 23:05 > Run = Level=Differential 2nd-5th Sun at 23:05 > Run = Incremental Mon-Sat at 23:05 > } > > Could be simplified to - > > Schedule { > Name = "dailyWithFullEveryOtherMonth" > > Run = Level=Full Jan,Mar,May,Jul,Sep,Nov 1st Sun at 23:05 > Run = Level=Differential Feb,Apr,Jun,Aug,Oct,Dec 1st Sun at 23:05 > Run = Level=Differential 2nd-5th Sun at 23:05 > Run = Incremental Mon-Sat at 23:05 > } > > Notes: Comma operators could be allowed in the specification of the month, > weekday, and time. Program logic would have to expand to all combinations. > Ex: Jan,Feb 1st Sun,Wed would have to expand to Jan 1st Sun, Jan 1st Wed, > Feb 1st Sun, Feb 1st Wed. > > > ---------- > > Heath Petersen > > Email: Heath@HPetersenFamily.com > > Cell: 507-220-2485 > > > > Health Services Leader > > Southwest Minnesota Chapter, Worthington > > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > > > > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel > > |
From: Kern S. <ke...@si...> - 2014-04-12 17:24:04
|
Hello Heath, On 04/12/2014 04:19 PM, Heath Petersen wrote: > http://www.bacula.org/5.2.x-manuals/en/main/main/Configuring_Director.html#SECTION001450000000000000000 > does not mention the comma operator. That is what I was going by. I > guess I should have tried it. Thanks for the information and quick > reply. I think you are right that the comma operator is not specified, but if you look at the BNF, you will see that multiple keywords for both months and days can be specified by separating them with spaces, which is actually the most common way of doing it. The BNF also shows the range specifications. > > Also, http://blog.bacula.org/support/feature-requests/ states to > submit feature requests in this manner. I will do it the way you > mention in the future. Thanks for noting that, the old website was rather difficult to maintain and modify, so it tended to get out of date quickly. The new site under Wordpress is much easier to update, so I have updated the page you refer to adding the preferred way to submit Feature Requests. Thanks for using Bacula, Best regards, Kern > Thank you. > > > Heath Petersen > > Email: Heath@HPetersenFamily.com > > Cell: 507-220-2485 > > > > Health Services Leader > > Southwest Minnesota Chapter, Worthington > > > > > On Sat, Apr 12, 2014 at 3:38 AM, Kern Sibbald <ke...@si...> wrote: >> Hello Heath, >> >> Thanks for using Bacula. >> >> I guess it is not much fun to read such a large manual, so perhaps I could suggest that it is fun to go off to a Bacula Admin I course -- all students love it, and in that course you learn about Bacula without having to read the manual. You also learn that commas between items such as Months and days of the week are perfectly well handled by Bacula. The same is true for ranges of months and days by separating the start and end days with a hyphen. >> >> Bottom line: this has been implemented in Bacula from the beginning. >> >> By the way, the best place to file a feature request is in the bugs database (features section). >> >> Best regards, >> Kern >> >> On 04/12/2014 12:22 AM, Heath Petersen wrote: >> >> Item 1: Allow combinations of parameters separated by commas >> in job schedules >> Date: 11 April 2014 >> Origin: Heath Petersen <Heath@HPetersenFamily.com> >> Status: >> >> What: The ability to allow combinations of parameters >> separated by commas would clean up some schedule >> definitions. >> >> Why: An example is the easiest way to explain this - >> >> Schedule { >> Name = "dailyWithFullEveryOtherMonth" >> >> Run = Level=Full Jan 1st Sun at 23:05 >> Run = Level=Differential Feb 1st Sun at 23:05 >> Run = Level=Full Mar 1st Sun at 23:05 >> Run = Level=Differential Apr 1st Sun at 23:05 >> . >> . Shortened for readability. >> . >> Run = Level=Differential Dec 1st Sun at 23:05 >> Run = Level=Differential 2nd-5th Sun at 23:05 >> Run = Incremental Mon-Sat at 23:05 >> } >> >> Could be simplified to - >> >> Schedule { >> Name = "dailyWithFullEveryOtherMonth" >> >> Run = Level=Full Jan,Mar,May,Jul,Sep,Nov 1st Sun at 23:05 >> Run = Level=Differential Feb,Apr,Jun,Aug,Oct,Dec 1st Sun at 23:05 >> Run = Level=Differential 2nd-5th Sun at 23:05 >> Run = Incremental Mon-Sat at 23:05 >> } >> >> Notes: Comma operators could be allowed in the specification of the month, >> weekday, and time. Program logic would have to expand to all combinations. >> Ex: Jan,Feb 1st Sun,Wed would have to expand to Jan 1st Sun, Jan 1st Wed, >> Feb 1st Sun, Feb 1st Wed. >> >> >> ---------- >> >> Heath Petersen >> >> Email: Heath@HPetersenFamily.com >> >> Cell: 507-220-2485 >> >> >> >> Health Services Leader >> >> Southwest Minnesota Chapter, Worthington >> >> >> >> >> ------------------------------------------------------------------------------ >> Put Bad Developers to Shame >> Dominate Development with Jenkins Continuous Integration >> Continuously Automate Build, Test & Deployment >> Start a new project now. Try Jenkins in the cloud. >> http://p.sf.net/sfu/13600_Cloudbees >> >> >> >> _______________________________________________ >> Bacula-devel mailing list >> Bac...@li... >> https://lists.sourceforge.net/lists/listinfo/bacula-devel >> >> |
From: Heath P. <Heath@HPetersenFamily.com> - 2014-04-12 19:54:16
|
On Sat, Apr 12, 2014 at 12:23 PM, Kern Sibbald <ke...@si...> wrote: > Hello Heath, > > On 04/12/2014 04:19 PM, Heath Petersen wrote: >> http://www.bacula.org/5.2.x-manuals/en/main/main/Configuring_Director.html#SECTION001450000000000000000 >> does not mention the comma operator. That is what I was going by. I >> guess I should have tried it. Thanks for the information and quick >> reply. > I think you are right that the comma operator is not specified, but if > you look at the BNF, you will see that multiple keywords for both months > and days can be specified by separating them with spaces, which is > actually the most common way of doing it. The BNF also shows the range > specifications. I am not fluent in BNF but still don't see where it shows that you can separate them by spaces. Would you mind cutting and pasting that part in a reply so I can understand it? >> >> Also, http://blog.bacula.org/support/feature-requests/ states to >> submit feature requests in this manner. I will do it the way you >> mention in the future. > Thanks for noting that, the old website was rather difficult to maintain > and modify, so it tended to get out of date quickly. The new site under > Wordpress is much easier to update, so I have updated the page you refer > to adding the preferred way to submit Feature Requests. > Thanks for updating this. I know how hard it is to keep documents / web pages up to date. > Thanks for using Bacula, > > Best regards, > Kern > >> Thank you. >> >> >> Heath Petersen >> >> Email: Heath@HPetersenFamily.com >> >> Cell: 507-220-2485 >> >> >> >> Health Services Leader >> >> Southwest Minnesota Chapter, Worthington >> >> >> >> >> On Sat, Apr 12, 2014 at 3:38 AM, Kern Sibbald <ke...@si...> wrote: >>> Hello Heath, >>> >>> Thanks for using Bacula. >>> >>> I guess it is not much fun to read such a large manual, so perhaps I could suggest that it is fun to go off to a Bacula Admin I course -- all students love it, and in that course you learn about Bacula without having to read the manual. You also learn that commas between items such as Months and days of the week are perfectly well handled by Bacula. The same is true for ranges of months and days by separating the start and end days with a hyphen. >>> >>> Bottom line: this has been implemented in Bacula from the beginning. >>> >>> By the way, the best place to file a feature request is in the bugs database (features section). >>> >>> Best regards, >>> Kern >>> >>> On 04/12/2014 12:22 AM, Heath Petersen wrote: >>> >>> Item 1: Allow combinations of parameters separated by commas >>> in job schedules >>> Date: 11 April 2014 >>> Origin: Heath Petersen <Heath@HPetersenFamily.com> >>> Status: >>> >>> What: The ability to allow combinations of parameters >>> separated by commas would clean up some schedule >>> definitions. >>> >>> Why: An example is the easiest way to explain this - >>> >>> Schedule { >>> Name = "dailyWithFullEveryOtherMonth" >>> >>> Run = Level=Full Jan 1st Sun at 23:05 >>> Run = Level=Differential Feb 1st Sun at 23:05 >>> Run = Level=Full Mar 1st Sun at 23:05 >>> Run = Level=Differential Apr 1st Sun at 23:05 >>> . >>> . Shortened for readability. >>> . >>> Run = Level=Differential Dec 1st Sun at 23:05 >>> Run = Level=Differential 2nd-5th Sun at 23:05 >>> Run = Incremental Mon-Sat at 23:05 >>> } >>> >>> Could be simplified to - >>> >>> Schedule { >>> Name = "dailyWithFullEveryOtherMonth" >>> >>> Run = Level=Full Jan,Mar,May,Jul,Sep,Nov 1st Sun at 23:05 >>> Run = Level=Differential Feb,Apr,Jun,Aug,Oct,Dec 1st Sun at 23:05 >>> Run = Level=Differential 2nd-5th Sun at 23:05 >>> Run = Incremental Mon-Sat at 23:05 >>> } >>> >>> Notes: Comma operators could be allowed in the specification of the month, >>> weekday, and time. Program logic would have to expand to all combinations. >>> Ex: Jan,Feb 1st Sun,Wed would have to expand to Jan 1st Sun, Jan 1st Wed, >>> Feb 1st Sun, Feb 1st Wed. >>> >>> >>> ---------- >>> >>> Heath Petersen >>> >>> Email: Heath@HPetersenFamily.com >>> >>> Cell: 507-220-2485 >>> >>> >>> >>> Health Services Leader >>> >>> Southwest Minnesota Chapter, Worthington >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Put Bad Developers to Shame >>> Dominate Development with Jenkins Continuous Integration >>> Continuously Automate Build, Test & Deployment >>> Start a new project now. Try Jenkins in the cloud. >>> http://p.sf.net/sfu/13600_Cloudbees >>> >>> >>> >>> _______________________________________________ >>> Bacula-devel mailing list >>> Bac...@li... >>> https://lists.sourceforge.net/lists/listinfo/bacula-devel >>> >>> > |
From: Kern S. <ke...@si...> - 2014-04-13 08:11:23
|
On 04/12/2014 09:54 PM, Heath Petersen wrote: > On Sat, Apr 12, 2014 at 12:23 PM, Kern Sibbald <ke...@si...> wrote: >> Hello Heath, >> >> On 04/12/2014 04:19 PM, Heath Petersen wrote: >>> http://www.bacula.org/5.2.x-manuals/en/main/main/Configuring_Director.html#SECTION001450000000000000000 >>> does not mention the comma operator. That is what I was going by. I >>> guess I should have tried it. Thanks for the information and quick >>> reply. >> I think you are right that the comma operator is not specified, but if >> you look at the BNF, you will see that multiple keywords for both months >> and days can be specified by separating them with spaces, which is >> actually the most common way of doing it. The BNF also shows the range >> specifications. > I am not fluent in BNF but still don't see where it shows that you can > separate them by spaces. Would you mind cutting and pasting that part > in a reply so I can understand it? After a bit more examination, it might just be that the BNF is not complete. Each of the <xxx-spec> items should be written as the date-spec is written: <date-spec> = <date> | <date-spec> That is it is defined recursively so that you can have multiple <date> values. All the <xxx-spec> (or most of them) are recursive, so in the <month-spec> there is a missing <month-spec> on the right side of the equation. Interesting that in 12 years no one has pointed it out (not even the author -- me). Clearly a few more examples could be useful. You get plenty in the course. I.e. one of the exercises on Schedules is (from memory) to write a Schedule for a year that does a Full backup bi-monthly on say Sunday at 3:05am, with a differential every Sunday except when the Full is run, and an Incremental all other days. About 1/3-1/2 of the students are able to figure it out. There should only be one backup per day. Best regards, Kern > >>> Also, http://blog.bacula.org/support/feature-requests/ states to >>> submit feature requests in this manner. I will do it the way you >>> mention in the future. >> Thanks for noting that, the old website was rather difficult to maintain >> and modify, so it tended to get out of date quickly. The new site under >> Wordpress is much easier to update, so I have updated the page you refer >> to adding the preferred way to submit Feature Requests. >> > Thanks for updating this. I know how hard it is to keep documents / > web pages up to date. > > >> Thanks for using Bacula, >> >> Best regards, >> Kern >> >>> Thank you. >>> >>> >>> Heath Petersen >>> >>> Email: Heath@HPetersenFamily.com >>> >>> Cell: 507-220-2485 >>> >>> >>> >>> Health Services Leader >>> >>> Southwest Minnesota Chapter, Worthington >>> >>> >>> >>> >>> On Sat, Apr 12, 2014 at 3:38 AM, Kern Sibbald <ke...@si...> wrote: >>>> Hello Heath, >>>> >>>> Thanks for using Bacula. >>>> >>>> I guess it is not much fun to read such a large manual, so perhaps I could suggest that it is fun to go off to a Bacula Admin I course -- all students love it, and in that course you learn about Bacula without having to read the manual. You also learn that commas between items such as Months and days of the week are perfectly well handled by Bacula. The same is true for ranges of months and days by separating the start and end days with a hyphen. >>>> >>>> Bottom line: this has been implemented in Bacula from the beginning. >>>> >>>> By the way, the best place to file a feature request is in the bugs database (features section). >>>> >>>> Best regards, >>>> Kern >>>> >>>> On 04/12/2014 12:22 AM, Heath Petersen wrote: >>>> >>>> Item 1: Allow combinations of parameters separated by commas >>>> in job schedules >>>> Date: 11 April 2014 >>>> Origin: Heath Petersen <Heath@HPetersenFamily.com> >>>> Status: >>>> >>>> What: The ability to allow combinations of parameters >>>> separated by commas would clean up some schedule >>>> definitions. >>>> >>>> Why: An example is the easiest way to explain this - >>>> >>>> Schedule { >>>> Name = "dailyWithFullEveryOtherMonth" >>>> >>>> Run = Level=Full Jan 1st Sun at 23:05 >>>> Run = Level=Differential Feb 1st Sun at 23:05 >>>> Run = Level=Full Mar 1st Sun at 23:05 >>>> Run = Level=Differential Apr 1st Sun at 23:05 >>>> . >>>> . Shortened for readability. >>>> . >>>> Run = Level=Differential Dec 1st Sun at 23:05 >>>> Run = Level=Differential 2nd-5th Sun at 23:05 >>>> Run = Incremental Mon-Sat at 23:05 >>>> } >>>> >>>> Could be simplified to - >>>> >>>> Schedule { >>>> Name = "dailyWithFullEveryOtherMonth" >>>> >>>> Run = Level=Full Jan,Mar,May,Jul,Sep,Nov 1st Sun at 23:05 >>>> Run = Level=Differential Feb,Apr,Jun,Aug,Oct,Dec 1st Sun at 23:05 >>>> Run = Level=Differential 2nd-5th Sun at 23:05 >>>> Run = Incremental Mon-Sat at 23:05 >>>> } >>>> >>>> Notes: Comma operators could be allowed in the specification of the month, >>>> weekday, and time. Program logic would have to expand to all combinations. >>>> Ex: Jan,Feb 1st Sun,Wed would have to expand to Jan 1st Sun, Jan 1st Wed, >>>> Feb 1st Sun, Feb 1st Wed. >>>> >>>> >>>> ---------- >>>> >>>> Heath Petersen >>>> >>>> Email: Heath@HPetersenFamily.com >>>> >>>> Cell: 507-220-2485 >>>> >>>> >>>> >>>> Health Services Leader >>>> >>>> Southwest Minnesota Chapter, Worthington >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Put Bad Developers to Shame >>>> Dominate Development with Jenkins Continuous Integration >>>> Continuously Automate Build, Test & Deployment >>>> Start a new project now. Try Jenkins in the cloud. >>>> http://p.sf.net/sfu/13600_Cloudbees >>>> >>>> >>>> >>>> _______________________________________________ >>>> Bacula-devel mailing list >>>> Bac...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bacula-devel >>>> >>>> |