search for: httnet

On 09/10/15, C Linus Hicks wrote: On 09/10/15, Robert Moskowitz wrote: ---------------- Quoted text ------------------------ Try this: rsync -ah --stats 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ --------------------- End Quote ---------------------------------- Sorry, I was too fast, not paying attention, you want this I believe: rsync -ah --stats root at 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ That will use the default port on the...

...-0400 Robert Moskowitz wrote: > > That will use the default port on the remote host, you can override > > that without specifying the -e if required using -p <port>. > > > $ rsync -ah --stats --delete -p 613 root at 192.168.129.2:/etc/dhcp/ > /home/rgm/data/htt/httnet/homebase/new/dhcp > Unexpected remote arg: root at 192.168.129.2:/etc/dhcp/ > rsync error: syntax or usage error (code 1) at main.c(1330) > [sender=3.1.1] > > So not there yet. :( From 'man rsync': -p, --perms This option causes the receiving rsync to set the destinat...

On 09/10/15, Robert Moskowitz wrote: ---------------- Quoted text ------------------------ I just tried the following: rsync -ah --stats "ssh -p613 -l root" 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httnet/homebase/new/root/ And it failed with: Unexpected remote arg: 192.168.192.2:/root/samba.PDC/ rsync error: syntax or usage error (code 1) at main.c(1330) [sender=3.1.1] I tried again with: rsync -ah --stats -e "ssh -p613 -l root" 192.168.192.2:/root/samba.PDC/ /home/rgm/data/htt/httne...

I am trying to rsync the named files under /etc for backup purposes. I tried: rsync -ah --stats --delete -e "ssh -p613 -l root" 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc The stats shows it sees all the files, but only moves the dir /etc/named and the files within it. It does not move the /etc/name* files (like /etc/named.conf). By file count, it is 'seeing' all the files, but not moving them.

On 09/10/2015 02:31 PM, C Linus Hicks wrote: > On 09/10/15, C Linus Hicks wrote: > > On 09/10/15, Robert Moskowitz wrote: > ---------------- Quoted text ------------------------ > > Try this: > rsync -ah --stats 192.168.192.2:/root/samba.PDC/ > /home/rgm/data/htt/httnet/homebase/new/root/ > --------------------- End Quote ---------------------------------- > > Sorry, I was too fast, not paying attention, you want this I believe: > > rsync -ah --stats root at 192.168.192.2:/root/samba.PDC/ > /home/rgm/data/htt/httnet/homebase/new/root/ > > T...

...t Moskowitz wrote: > >>> That will use the default port on the remote host, you can override >>> that without specifying the -e if required using -p <port>. >> >> $ rsync -ah --stats --delete -p 613 root at 192.168.129.2:/etc/dhcp/ >> /home/rgm/data/htt/httnet/homebase/new/dhcp >> Unexpected remote arg: root at 192.168.129.2:/etc/dhcp/ >> rsync error: syntax or usage error (code 1) at main.c(1330) >> [sender=3.1.1] >> >> So not there yet. :( > >From 'man rsync': > > -p, --perms This option causes the...

On 09/10/15, Robert Moskowitz wrote: --------------- Quoted text ------------------ SSh is not parsing the port the way http does, it seems: $ rsync -ah --stats root at 192.168.129.2:613:/etc/dhcp/ /home/rgm/data/htt/httnet/homebase/new/dhcp ssh: connect to host 192.168.129.2 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1] The reason why I change my SSH port is a simple way to keep port knocker...

...> On Mon, 7 Sep 2015 13:05:59 -0400 > Robert Moskowitz wrote: > >> I am trying to rsync the named files under /etc for backup purposes. >> I tried: >> >> rsync -ah --stats --delete -e "ssh -p613 -l root" >> 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc >> >> The stats shows it sees all the files, but only moves the >> dir /etc/named and the files within it. >> >> It does not move the /etc/name* files (like /etc/named.conf). >> >> By file count, it is 'seeing' all the files, but no...

On Mon, 7 Sep 2015 13:05:59 -0400 Robert Moskowitz wrote: > I am trying to rsync the named files under /etc for backup purposes. > I tried: > > rsync -ah --stats --delete -e "ssh -p613 -l root" > 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc > > The stats shows it sees all the files, but only moves the > dir /etc/named and the files within it. > > It does not move the /etc/name* files (like /etc/named.conf). > > By file count, it is 'seeing' all the files, but not moving them. Hi Robert...

On 4/12/2017 7:25 PM, Robert Moskowitz wrote: > I am writing my howto on BIND for Centos7. Mine is running on > Centos7-arm. You can see some of the basics I have done at: > > file:///home/rgm/data/htt/httnet/homepage/Centos7-armv7.html noone else can see your local file system -- john r pierce, recycling bits in santa cruz

Le 13/04/2017 ? 04:25, Robert Moskowitz a ?crit : > I am writing my howto on BIND for Centos7. Mine is running on > Centos7-arm. You can see some of the basics I have done at: > > file:///home/rgm/data/htt/httnet/homepage/Centos7-armv7.html > > I have a caveat I learned with dealing with SELinux and BIND there. You sent a link to a local file (file://) so unfortunately I can't access it. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://w...

Hi, I just installed CentOS 7 on a public server. I'd like to setup BIND as a primary DNS server for a few domains. Until now, all my public machines were running Slackware Linux, and setting up BIND on a Slackware machine is relatively easy. In its out of the box configuration, it has a bone-headed caching nameserver role, which is quite easy to expand to a primary nameserver. Here's my

...inus Hicks wrote: >> On 09/10/15, Robert Moskowitz wrote: >> >> --------------- Quoted text ------------------ >> SSh is not parsing the port the way http does, it seems: >> >> $ rsync -ah --stats root at 192.168.129.2:613:/etc/dhcp/ >> /home/rgm/data/htt/httnet/homebase/new/dhcp >> ssh: connect to host 192.168.129.2 port 22: No route to host >> rsync: connection unexpectedly closed (0 bytes received so far) >> [Receiver] >> rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1] >> >> The reason why I c...

...3 -0700 (PDT) Mark Milhollan wrote: > On Mon, 7 Sep 2015, Carl E. Hartung wrote: > >On Mon, 7 Sep 2015 13:05:59 -0400 > >Robert Moskowitz wrote: > > >> rsync -ah --stats --delete -e "ssh -p613 -l root" > >> 192.168.192.2:/etc/name* /home/rgm/data/htt/httnet/homebase/new/etc > > >Why '-e' (specify remote shell to use)? Are these systems running > >disparate operating systems? > > -e specifies the *local* transport command to use What?! Straight from the documentation: " -e, --rsh=COMMAND specify the...

...y On Mon, Sep 7, 2015 at 1:05 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: > I am trying to rsync the named files under /etc for backup purposes. I > tried: > > rsync -ah --stats --delete -e "ssh -p613 -l root" 192.168.192.2:/etc/name* > /home/rgm/data/htt/httnet/homebase/new/etc > > The stats shows it sees all the files, but only moves the dir /etc/named > and the files within it. > > It does not move the /etc/name* files (like /etc/named.conf). > > By file count, it is 'seeing' all the files, but not moving them. > > &gt...

On 09/11/2015 10:21 AM, C Linus Hicks wrote: > On 09/10/15, Robert Moskowitz wrote: > > --------------- Quoted text ------------------ > SSh is not parsing the port the way http does, it seems: > > $ rsync -ah --stats root at 192.168.129.2:613:/etc/dhcp/ > /home/rgm/data/htt/httnet/homebase/new/dhcp > ssh: connect to host 192.168.129.2 port 22: No route to host > rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] > rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.1] > > The reason why I change my SSH port is a simple...

I am writing my howto on BIND for Centos7. Mine is running on Centos7-arm. You can see some of the basics I have done at: file:///home/rgm/data/htt/httnet/homepage/Centos7-armv7.html I have a caveat I learned with dealing with SELinux and BIND there. On 04/11/2017 01:05 PM, Nicolas Kovacs wrote: > Hi, > > I just installed CentOS 7 on a public server. I'd like to setup BIND as > a primary DNS server for a few domains. > > Until...