Re: move client-config to a subdir of __TOPDIR__

Tino Schwarze <[email protected]>
Newsgroups gmane.comp.sysutils.backup.backuppc.devel
Message-ID <[email protected]>
Hi Mike,

On Wed, Mar 23, 2011 at 10:22:37PM +0100, Fresel Michal - hi competence e.U. wrote:

> well - prefer "up and running" packages :)
 
I've not yet bothered to try or build a package of BackupPC - since in
my installation, everything is in /backup/backuppc anyway.

> as the /etc should contain just the config for (localhost-specific) i would say "backuppc-config" may stay there ...
> 
> Reading the "Configuration file" on wikipedia it seems for the client config there might be an exeption:
> "Server processes often use configuration files stored in /etc, but they may also use their installation directory or a location defined by the system administrator."
> 
> as this are not really localhost (server) specific the admin is allowed to specify another path - so client-credentials are allowed to be somewhere else?
> Maybe usefully encrypted together with the data?

It's not an issue of BackupPC installation where you put your ssh keys.
If your are using multiple keys for client access, you need to specify
them in your per-client configuration anyway and ssh doesn't care
whether you use "-i /home/someuser/.ssh/id_dsa-client1" or "-i
/data/encrypted/client-keys/client1"

Note that BackupPC's main distribution is just a .tar.gz, not a
Debian/XYZ binary package. You might want to contact your package
maintainer about the default home directory of your backuppc user etc.
It's a detail of the setup (context) of BackupPC, not a detail of
BackupPC itself.

Or am I missing your point?

HTH,

Tino.

> 
> Greetings 
> Mike
> 
> Am 23.03.2011 um 21:55 schrieb Les Mikesell:
> 
> > On 3/23/2011 3:29 PM, Fresel Michal - hi competence e.U. wrote:
> >> hi Jeffrey,
> >> 
> >> 
> >>> data goes in /var
> >>> configurations go in /etc
> >>> It's a *nix standard. But you are free to violate if you want...
> >> 
> >> well ... so we are willing to break the Standards of LSB and walk the way of a secure implementation....
> > 
> > The .deb/.rpm distribution packagers usually follow the standard, but if 
> > you do your own install from the sourceforge tarball you should be able 
> > to put things where you want.  It has been a long time since I set one 
> > up, but I like having everything under one directory so if you keep a 
> > drive image offsite you are sure to have the current configuration.
> > 
> > -- 
> >   Les Mikesell
> >    [email protected]
> 
> 
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software 
> be a part of the solution? Download the Intel(R) Manageability Checker 
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> BackupPC-devel mailing list
> [email protected]
> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
> Wiki:    http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/

-- 
"What we nourish flourishes." - "Was wir nähren erblüht."

www.tisc.de

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
BackupPC-devel mailing list
[email protected]
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.