That's correct. The code winds up looking either in /etc, or in $TOPDIR/conf, neither of which is correct. On FreeBSD, it would go in /usr/local/etc/BackupPC (or /usr/local/etc/backuppc, whichever).
Tony Shadwick OSS Solutions Craig Barratt wrote: > Tony writes: > >> Anyhoo...I tend to think we have at very least a bug in configure.pl, >> but moreover we need to be a bit more flexible on being able to define >> confDir. As was mentioned before, having the option to pass it on the >> command line would clear this right up. > > There are two different options for configure.pl (starting in > BackupPC-3.0.0beta1): > > --config-dir CONFIG_DIR > Configuration directory for new installations. Defaults to > /etc/BackupPC with FHS. Automatically extracted from --con- > fig-path for existing installations. > > --config-path CONFIG_PATH > Path to the existing config.pl configuration file for BackupPC. > This option should be specified for batch upgrades to an exist- > ing installation. The option should be omitted when doing a > batch new install. > > Use --config-dir for a new installation. Use --config-path only for > an upgrade. > > I didn't retest the --config-dir option though. Just to confirm: you are > using > > configure.pl --config-dir XXX > > in BackupPC 3.0.0, and it doesn't work? > > Craig ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
