On Sat, Feb 14, 2004, Scott Hasse wrote:
> 1) (Sorry, first more of a user list question) Before I bother, is there
> a different strategy that people are using for backup that is already
> integrated within openpkg.
No, there is no such package. Amanda would be fine. Go for it.
> 2) Amanda normally uses inetd/xinetd. This, of course, makes
> cross-platform packaging more difficult. I have not yet been able to
> find an example openpkg rpm that uses inetd/xinetd to see how that
> problem has been solved. Alternately, it would be possible to use a
> package like tcpserver to avoid using inetd. I am not sure which is the
> better approach, or if there is another better approach I haven't
> thought of.
We usually prefer the "standalone server" approach, i.e., without
[x]inetd, both for independency and performance reasons. But as a
first cut you could also depend on the xinetd package. It is certainly
acecptable at the first cut.
> 3) It is normally sane to compile amanda with a restricted list of udp
> ports. This makes firewall configuration a bit simpler and somewhat
> more secure. However deciding which and how many ports depends on the
> installation. I could implement a with_restricted_ports build option,
> but are there other ways of solving this?
If it is a compile-time only option (no run-time alternative) the only
ways are to use a hard-coded (but hopefully reasonable to apply for
most situations) list or you have to use an "%option with_xxx". Other
possibilities do not exist, except you want to patch Amanda to make the
list a run-time option by reading the stuff from a config file.
> 4) amanda includes client and server portions. Would it be best to have
> separate packages, or include a "with_client_only" mode?
An "%option with_server no" would be the best IMHO. This way one gets
the client by default and with "--with server" one get client & server.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]