On 15/7/17 13:00, Paul Fox wrote:
B wrote:
> On Fri, 14 Jul 2017 18:56:19 -0400
> Paul Fox wrote:
>
> > i confess i haven't been following this thread in all its gory detail,
>
> The BackupPC god absolves you (although, it is the BPC v.3x god, so
> you'll need to upgrade the
B wrote:
> On Fri, 14 Jul 2017 18:56:19 -0400
> Paul Fox wrote:
>
> > i confess i haven't been following this thread in all its gory detail,
>
> The BackupPC god absolves you (although, it is the BPC v.3x god, so
> you'll need to upgrade the confessionnal if you want to also be absolv
On Fri, 14 Jul 2017 18:56:19 -0400
Paul Fox wrote:
Just a precision for B.Katz: I also have a script that creates an
_INSTALLED_PKGS.txt file from the usual command (debian),
launched as a pre-backup command to be able to easily reconstruct
the full exact working system from a minimal install.
J
On Fri, 14 Jul 2017 18:56:19 -0400
Paul Fox wrote:
> i confess i haven't been following this thread in all its gory detail,
The BackupPC god absolves you (although, it is the BPC v.3x god, so
you'll need to upgrade the confessionnal if you want to also be absolved
by the v.4.x one.)
> but i sus
B wrote:
> On Fri, 14 Jul 2017 18:22:54 -0400
> Bob Katz wrote:
>
> > Oh boy I get it!!! I can't believe how stupid I was about that.
>
> Me too ;-p)
>
> > Well, doesn't this mean I have to establish a whole bunch of modules
> > with a different path for each module, in orde
On Fri, 14 Jul 2017 18:22:54 -0400
Bob Katz wrote:
> Oh boy I get it!!! I can't believe how stupid I was about that.
Me too ;-p)
> Well, doesn't this mean I have to establish a whole bunch of modules
> with a different path for each module, in order to back up everything
> EXCEPT the ba
Dear Stefan, you are so kind! This helps a lot. Yes, I'm plodding my way
through. You wrote:
[Backup-Data-Folder]
## Next, set the path you want backed up. Be sure to use a trailing
slash
path= /
Please don't do that:
o a Linux system has virtual file systems mounted
Hi Bob
On 14.07.2017 21:32, Bob Katz wrote:
... snip ...
>
>
> 2017/07/14 15:06:17 [3292] connect from localhost (::1)
> 2017/07/14 15:06:17 [3292] rsync denied on module Backup-Data-Folder
> from localhost (::1)
>
... snip ...
>
> ###
Still not much progress but I've simplified things. In Fedora, rsync
daemon is supposed to be run by systemctl. But I am pretty sure my
attempt to create a service for rsync as a daemon has failed somewhere.
So I'm debuggin by using the simple command line: sudo rsync ---daemon
By the way, rsync
Thanks. Well, first I have to ensure that inetd and no other mechanism I
foolishly initiated in my efforts is running. I'm working on that now.
But is there a point to running sudo rsync if the object is to use
systemctl to run the daemon? Is that for a test or permanent? Yes, I'm
confuse
Running BackupPC 3 on Debian Wheezy. Ran out of inodes on 250 GB
filesystem, max inodes was 15 million. Can the nightly cleanup now run
and maybe release some idodes from the oldest backups?
Since the filesystem is Ext4 I can not increase max inodes. Would it
reduce the need of inodes if I reduced
--On Thursday, July 13, 2017 12:03 PM -0400 Bob Katz
wrote:
There must be a foolproof way of displaying running daemons, finding out
the PID and killing it. The PS command that everyone is fond of does not
show the daemon is runnning, I don't believe.
If ps doesn't see it, then it's not the
--On Thursday, July 13, 2017 4:37 PM + Michael Stowe
wrote:
At this point, I'd recommend
sudo rsync --daemon --foreground --verbose
So you can actually tell what's happening.
According to the man page, --foreground should be --no-detach. That keeps
the daemon from disappearing and cau
13 matches
Mail list logo
