Beyond being a satisfied user and telling other people about it, everyone
is encouraged to add links to L<http://backuppc.sourceforge.net>
-(I'll see then via Google) or otherwise publicize BackupPC. Unlike
+(I'll see them via Google) or otherwise publicize BackupPC. Unlike
the commercial products in this space, I have a zero budget (in both
time and money) for marketing, PR and advertising, so it's up to
all of you! Feel free to vote for BackupPC at
=head2 Step 3: Setting up config.pl
After running configure.pl, browse through the config file,
-__INSTALLDIR__/conf/config.pl, and make sure all the default settings
+__TOPDIR__/conf/config.pl, and make sure all the default settings
are correct. In particular, you will need to decide whether to use
smb, tar or rsync transport (or whether to set it on a per-PC basis)
and set the relevant parameters for that transport method.
=item Mac OS X
In general this should be similar to Linux/Unix machines.
-Mark Stosberg reports that you can also use hfstar.
+Many users have reported success using xtar, which also
+backs up the Mac OS X resource forks.
+
+Other choices include rsync and Mark Stosberg reports that you
+can also use hfstar.
See L<http://fink.sourceforge.net/pdb/package.php/hfstar>.
=item SSH Setup
running. Therefore, when it is time to run BackupPC_nightly, no new
backups are started and BackupPC waits until all backups have finished.
Then BackupPC_nightly is run, and until it finishes no new backups are
-started. If BackupPC_nightly is slow, the settings
+started. If BackupPC_nightly takes too long to run, the settings
+$Conf{MaxBackupPCNightlyJobs} and $Conf{BackupPCNightlyPeriod} can
+be used to run several BackupPC_nightly processes in parallel, and
+to split its job over several nights.
=back
=head1 Copyright
-Copyright (C) 2001-2004 Craig Barratt
+Copyright (C) 2001-2005 Craig Barratt
=head1 Credits