On 01/20/10 08:16 AM, Phil Stracchino wrote:
> I've several times now tried to look up resource specifications in the
> Bacula online documentation.  (In this particular case, I'm trying to
> look up some information for an answer to a user question.)  I know
> that, buried somewhere in the documentation, there are sections that
> describe every resource and all of the possible directives each resource
> can contain.  However, try as I might, I can never find it, either from
> the table of contents, from the index, or by a web search.  You just
> have to Know Where It Is.
>
> I suggest that the documentation needs a single complete Configuration
> Reference appendix that goes through each of the possible configuration
> files (bacula-dir.conf, bacula-fd.conf, bacula-sd.conf, bconsole.conf,
> bat.conf) listing every resource that can exist in that file and every
> directive that is legal - and every directive that is *required* - in
> each resource in that file.  It need not explain the directives in
> detail, as long as each directive has a link to where it *is* explained
> in detail.  The purpose of this chapter would be to provide a complete
> configuration reference in one place, something that is currently either
> missing, or very difficult to find unless you already know where to find it.
>

Thats a great idea! I could probably find some time to help out with 
that project.


-- 
   Robert W Hartzell
bear at rwhartzell.net
   RwHartzell.Net

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to