of the ssh authorized_keys directories and files so that if you are
not using the standard location for authorized_keys files
($HOME/.ssh/authorized_keys) and instead using the
/etc/ssh/sshd_config option "AuthorizedKeysFile" you can then specify
where that will be.

For example, if your /etc/ssh/sshd_config has:

AuthorizedKeysFile /etc/ssh/authorized_keys/$u

then you could specify in the rdiff-backup definition the following
parameters:

...
        ssh_dir => "/etc/ssh/authorized_keys",
        authorized_keys_file => "${hostname}",

to create the file /etc/ssh/authorized_keys/${hostname} instead of the
default location (if unspecifed, the default is used).

set the backuptag on crabgrass to not use the default one, otherwise
it wont be collected

when you have two rdiff-backup calls, then the User is a Duplicate
definition, i think the only way to do it is to have a variable that
you can set to turn off user handling (which we make $installuser and
$usermanage be consistant with $installkey and $keymanage), which is
set true by default, but when you have a second rdiff call on a host,
you can set it to false

change the $host variable to no longer use the $user variable, that way
multiple rdiff's can be instantiated for a particular host, with different
name variables
in order to do that, the class also has to have the $installkeys variable that
can be passed to backupninja::client::key so that the second rdiff instantiation would
set installkeys => false, otherwise there will be an attempt to duplicate the resource

by their name variable