opkia.blogg.se

The error I get on the receiving machine ( 192.168.1.2) is: nc -q 1 -l -p 32934 | tar xv

I've tried the netcat-openbsd and netcat-traditional packages with no luck whatsoever. So, after a good at few hours of attempting to pull myself out of the morass of my own ignorance (or, as I like to think of it, to pull myself up by my own bootstraps) I came up with some useful facts.īut first of all, what led me on this rabbit trail instead of simply accepting the current best answer was this: nc is an unbelievably cool program that resolutely fails to work for me. So, to reiterate, how do I set up a similar network with TCP? I'm not sure if there's a way to tweak my NFS settings to handle huge files better, but I'd like to see if running an rsync daemon over plain old TCP works better than rsync over NFS. I'm using rsync to transfer them, and the command (on 192.168.1.2) is $ rsync -avxS /mnt/network1 ~/somedir The files average about half a gigabyte a piece, and the directories are all between 15 and 50 gigabytes. The above works fine, but the files and directories are huge. Where /mnt/network1 is specified in /etc/fstab asġ92.168.1.1:/home /mnt/network1 nfs noauto,user,exec,soft,nfsvers=2 0 0Īs well as in /etc/exports (using the syntax of that file), on the first netbook. On the first netbook and $ sudo ifconfig eth0 192.168.1.2 up To network them, I type $ sudo ifconfig eth0 192.168.1.1 up & ping -c 10 -s 10 192.168.1.2 & sudo /etc/init.d/nfs-kernel-server start

Hardware-wise, I am using an ethernet crossover cable to network two netbooks. I am having some trouble with NFS, and I'd like to try using just plain old TCP.