gregrwm wrote at about 08:42:44 -0500 on Sunday, October 13, 2013:
 > as for BackupPC_dump, either it ought to feedback the same activity
 > awareness as BackupPC_serverMesg, or its documentation ought to warn of the
 > risk and advise against its use.

Why? BackupPC_dump (along with several other supporting routines) were
not designed to be run alone. As Les mentioned, when run manually,
BackupPC is designed to be run from the web interface and if you do
want to use the command line, then you use BackupPC_serverMesg.

It is classic *nix philosophy for more complex routines to be built
from a sequence of smaller building-block routines. It is not the
responsibility of the building-block routine to remind you that it is
just a building block. Since I don't believe the BackupPC
documentation ever suggests running BackupPC_dump alone (at least
without mentioning that it should be sent as a server message), why
should it be the responsibility of the BackupPC_dump routine to warn
people about things they were never advised to do in the first
place... especially since there are an infinite number of such things
potentially...
 

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/