Ross Boylan wrote:
Package: postgresql
Version: 7.4.7-1
Severity: wishlist
Since I tend to use postgres, I'd like to use the flavor of bacula
that works with postgres. Unfortunately, there are a couple of RC
bugs against the package, and the maintainer has indicated he needs
help.
I filed those RC bugs myself (well, actually i raised their importance
to 'RC' in order to attract the attention of people participating in the
BSP last weekend).
I can probably get things working on my system, but my knowledge of
what assumptions are and are not reasonable to make, where to find
configuration setttings, etc, is slight. In other words, with luck I
may be able to produce a postinst that works for me, but it probably
won't be that great for general use.
Well, almost everything is welcome.
If you could help, even providing hints, that would be terrific.
indeed
It may be that the range of possible setups is so great that automatic
handling of the general case is unrealistic. Even so, something that
worked for the stock Debian setup would be useful; clearly, the sys
admin would need a way to bypass it if they had an unusual setup.
They already have it: do not create tables automatically
Some issues that occur to me:
The current script asks for an admin password, but I don't think the default
postgres setup has one (access controlled via unix postgres account).
indeed. That is there until i got a chance to actually behave
differently with local/remote hosts.
Is there a standard place to get info on database location, superuser
identity, etc?
Not really, AFAIK. Dbconfig-common *should* help with that,
What user should bacula keep its data under (bacula? backup?).
bacula, of course.
These are undoubtedly addressed in docs somewhere (and the scripts
provided have an implicit answer to the last question at least).
Yes :-)
But any suggestion/comments are indeed appreciated. Thanks.
J.L.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
