Ignore affected rows in UPDATE_DB

We get an error  message from UPDATE_DB , when
the number of affected rows is < 1.

In some cases, its ok to have no affected rows,
like in "update all volumes from all pools", when
there is a pool with no volumes inside.

Fixes #62: update all volumes from all pools gives error when a pool doesnt contain volumes

Signed-off-by: Marco van Wieringen <marco.van.wieringen@bareos.com>
fixes ubuntu configuration

Signed-off-by: Marco van Wieringen <marco.van.wieringen@bareos.com>
Fix Makefile rules for generating configure and config.h.in
Set some more sane defaults.

Still its better to explicitly set the dirs to where you want
them to be and to not depend on changing defaults.
Rebuild configure.
Send the catalog backup bootstrap file by mail

Having the bootstrap of the backupcatalog job is crucial
for disaster recovery.
Unfortunately, the default config didn't do that until now.

Now we automatically mail the bootstrap file of the backupcatalog job.

Also, we have now extended the BackupCatalog FileSet to include the
sysconfdir.

Fixes #24: Automatic sending of BSR (at least of the Catalog DB) via email