I'd love to include robust systemd templates and clearly written docs in
the vanilla BackupPC release (and on the Wiki). Previously, the package
managers had to include their own favorite flavors since the upstream
release doesn't include any. That presents problems, such as having many
different
Awesome news. I have been waiting for this day for 10+ years.
Thanks
The current Fedora / EPEL package supplies a SystemD unit file but it uses
type=oneshot which I don't agree with (although it works). I'm currently
working on taking over maintenance of the package since the current
m
On Fri, Mar 10, 2017 at 12:27 PM, Moorcroft, Mark (ARC-TS)[Analytical
Mechanics Associates, INC.] wrote:
>
>
> I’m curious since el7 has been the current OS for a pretty long time why
> the “new” version of BackupPC defaults to init.d? I will probably wait for
> the epel package to appear before
I’m curious since el7 has been the current OS for a pretty long time why the
“new” version of BackupPC defaults to init.d? I will probably wait for the epel
package to appear before I upgrade. But I gave consideration to piecing
together a 4.x install to replace 3.x, but locate things so when t
I bumped into this very problem when experimenting with an upgrade from a
package.
After removing the package via the package manager the original
/init.d/backuppc startup script remained.
It makes checks for v2 settings. It needs to be replaced with the proper
init script from the v4 relea
On March 9, 2017 11:47:09 PM Pavel Hofman wrote:
> mph,
>
> Actually we are based on drives only. I could make a huge 10TB tar and
> put it somewhere but the idea of conversion and having all the backupcs
> together...
Agreed! A 10TB tar file on spinning media not practical. You already have
Teemu,
Copy the ubuntu based init script into your old one. You can find it in
the init.d folder.
Do you run the makeShift command?
Cheers,
mph
On March 9, 2017 11:44:57 PM Teemu Pirttikoski
wrote:
Hey there,
can anyone assist me on my problem, where I've got working installation of
Mixing a package-based install and manually installing from the tarball can
create issues.
I don't believe these error messages are from BackupPC. Perhaps the v3
systemd startup scripts are doing some error checking that doesn't work for
4.0.
Does /etc/backuppc/config.pl look like a valid v4 con
