HI
> The values in your config.pl script appear to be correct. The
> "Invalid argument" error is a protocol-level error. I'll need some
> more information to figure out what's going on.
ok, let's go on!
> What ftp server are you running?
as i said, that's an internet site; there's a ProFTPD 1
> Alternatively, set up the tunnel in DumpPreShareCmd instead
> of DumpPreUserCmd.
> Then you will be using a new tunnel for each share.
May I be using the same TCP ports for it?
That is my only concern right now...
--
> I have (successfully) been using a script to do this for the
> past few months. I copied this from somewhere else (the wiki
> perhaps) and have tuned locally since then...
>
> I created a script in /etc/backuppc/scripts/hostname.sh
> #!/bin/bash TERM=vt100 /usr/bin/screen -d -m -S hosttunnel
Craig Barratt wrote:
> Oblivian,
>
> As you point out, there isn't a general method for merging per-client
> settings with the global ones.
>
> However, in 3.2.0beta0 there is a new config variable
> $Conf{RsyncArgsExtra} which is combined with $Conf{RsyncArgs}.
> The purpose is exactly for your
Boniforti Flavio wrote:
>> Alternatively, set up the tunnel in DumpPreShareCmd instead
>> of DumpPreUserCmd.
>> Then you will be using a new tunnel for each share.
>
> May I be using the same TCP ports for it?
> That is my only concern right now...
As long as the other ssh has gone away and is n
> But, a generic vpn would make life simple.
I would really *love* to set up a VPN: can you help? I already have VPN
configured on the server (Windows 2003 SBS SP2), I (think) I just need
some command-line linux client, which would open the VPN connection
(DumpPreUserCmd) and having transferred a
Boniforti Flavio wrote:
>> But, a generic vpn would make life simple.
>
> I would really *love* to set up a VPN: can you help? I already have VPN
> configured on the server (Windows 2003 SBS SP2), I (think) I just need
> some command-line linux client, which would open the VPN connection
> (DumpPr
Il 14.04.09 16:55, "Les Mikesell" ha scritto:
> I happen to like openvpn running in peer to
> peer mode where you end up with a process and tunnel interface per
> instance.
OK, so I will take a look at openvpn. Leaving the VPN open is not a problem,
of course...
Thanks,
F.
---
Hello list!
This is the log from my last attempt to sync a directory containing 2 big
files:
Executing DumpPreUserCmd: /var/lib/backuppc/tunnel.sh -fC
administra...@mail.omvsa.ch -L 8874:127.0.0.1:873 sleep 60
SSH started successfully.
incr backup started back to 2009-04-10 17:33:03 (backup #2) f
Boniforti Flavio wrote:
>
>
> Il 14.04.09 16:55, "Les Mikesell" ha scritto:
>
>> I happen to like openvpn running in peer to
>> peer mode where you end up with a process and tunnel interface per
>> instance.
>
> OK, so I will take a look at openvpn. Leaving the VPN open is not a problem,
> of
Hi again,
A future option I really would love to see, is the ability to create
several sets of global/universal of exlude/include filters and being
able to just "tick" one or more set of filters that apply to the
different clients. And then of course have the option to set filters
specific to
Hi Thanks for the support. I installed
the File:Listing module and my backups
are working now.
>>> Craig Barratt 4/13/2009 11:33 PM >>>
Tim writes:
> This is a new install so I thought I would try the beta version
> do you recommend I go back to the stable version?
If you are willing to test t
Boniforti Flavio wrote:
> Hello list!
>
> This is the log from my last attempt to sync a directory containing 2 big
> files:
>
> Executing DumpPreUserCmd: /var/lib/backuppc/tunnel.sh -fC
> administra...@mail.omvsa.ch -L 8874:127.0.0.1:873 sleep 60
> SSH started successfully.
> incr backup starte
> As long as the other ssh has gone away and is no longer
> listening on the
> local forwarding port you should be able to start another instance.
> It if is a problem you could wrap the ssh command in a script
> that sleeps a few seconds first to make sure the previous run
> has time to clos
Hallo Matthias,
> Whats happen after this sleep of 60 seconds? I would believe
> that ssh stop the tunnel.
> And than rsync read this EOF.
Mmmhhh... Well, could it be that for some reason there has been a
timeout greater than 60 seconds and *thus* the ssh tunnel shut down,
while rsync was waitin
15 matches
Mail list logo
