Currently, it's very hard to come up with the "Fedoran Way" of configuring Bacula. I'm a newbie with it, but, I think, you could add a fabulous guide in a README.Fedora file; like some other packages have.
The README.Fedora could contain pointers on what to do to get it up and running ASAP. Don't try to make it a supplement for the docs (pdf files)... just add the key notes, like:
- Remember to change the password placeholders to some other password or it won't start while using service (took me 5 hours to figure this out)
I'm in the middle of the configuration so I can't suggest you any more. I'll try tu update this feature request with suggestions of the contents of the README.Fedora file.
The "bail out of the init script if passwords are still the default" was a gotcha for me as well. Maybe the init scripts should say something more specific than "Error: Not been configured" ?
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This bug applies to the bacula in the EPEL 5 repos. Can someone please change the Version field in this bugzilla entry so it doesn't get auto-closed?
Wait, this just changed from EPEL5 to F14... it is a bug in EPEL5.
Changed back to EPEL5.
why did this change to EPEL5 again? It's a feature request...
Excuse me. I have misunderstood previous comment. Feel free to move it back to Fedora.
(In reply to comment #8)
> Excuse me. I have misunderstood previous comment. Feel free to move it back to
These are just some points, that should be mentioned in the future README file:
* a user must configure bacula daemons after install (before starting)
* passwords that include "__PASSWORD@@" are not allowed
* only one package from bacula-director-postgresql, bacula-director-mysql, bacula-director-sqlite should be installed at the same time or user must configure alternatives properly (since bacula-dir points to one of the binaries from these packages)
This can be considered as well:
Added a README.Fedora file in rawhide(5.2.4).