Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Has anyone gotten rsync to work on the DNS-323?
I have telnet access using the 'fun_plug' trick with KRH's rar file
http://sconk.se/dns323/dns-323.rar. The rar archive included a
rsync binary (also one at http://dns323.info/). However, rsync
needs a remote shell (usually ssh or rsh) and I don't think the
DNS-323 has those remote shell binaries.
Is anyone successfully using rsync?
\\Mig
Offline
rsync does not need a remote shell it will work happily on any locally mounted remote storage.
Offline
How can you locally mount remote storage on the DNS-323?
Offline
mig,
Install telnet on DNS-323 and use the mount command, alternatively the same can be achieved from the other machine, rsync exists on various platforms.
Offline
WOW!! I didn't realize the DNS-323 has NFS. This is great.
I was successful in mounting a file system /data from a Kurobox running
Red Hat FC4 to my DNS-323 on /mnt/data
For anyone who wants to NFS mount on the DNS-323 here is what I did:
Logon as root on my Kurobox (FC4) 192.168.1.12
1. added this line to /etc/exports
/data 192.168.1.0/24(rw,no_root_squash,sync,no_subtree_check)
2. made sure NFS service was running by using the command
# /sbin/chkconfig nfs on
# /etc/init.d/nfs restart
3. exported the /data file system with the command
# /usr/sbin/exportfs
telnet to the DNS-323 192.168.1.11
1. created the mount point with the command
# mkdir /mnt/data
# chmod 777 /mnt/data
2. add this line to /etc/fstab with vi
192.168.1.12:/data /mnt/data nfs bg,soft,rsize=8192,wsize=8192 0 0
3. mounted the NFS fs wth the command
# mount -a
The three commands on the DNS-323 have to be put into the fun_plug script to survive a reboot.
You could use the following script 'mount_nfs.sh' (script must be executable # chmod +x mount_nfs.sh)
#!/bin/sh
# file: mount_nfs.sh
mkdir /mnt/data
chmod 777 /mnt/data
echo "192.168.1.12:/data /mnt/data nfs bg,soft,rsize=8192,wsize=8192 0 0" >> /etc/fstab
mount -a
Now I can copy all the files from the KuroBox /data to the RAID 1 array of the DNS-323
with the rsync command:
# rsync -a /mnt/data /mnt/HD_a2/data
Offline
the rsync command: # rsync -a remoteHost:/remote_dir /local_dir
fails with the following errors:
rsync: Failed to exec ssh: No such file or directory (2)
rsync error: error in IPC code (code 14) at pipe.c(86) [receiver=2.6.9pre3]
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in IPC code (code 14) at io.c(453) [receiver=2.6.9pre3]
I believe this is because rsync tries to connect via ssh (or optionally rsh) which DNS-323
does not have binaries for.
I did get rsync to work, but I had to setup a rsync daemon on the remote machine.
As root on the remote machine, Kurobox (FC4) 192.168.1.12
1. I created the /etc/rsyncd.conf file:
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsync.lock
[data]
path = /data
comment = data area
use chroot = no
hosts allow = 192.168.1.11
list = yes
auth users = root
secrets file = /etc/.rs_sec
2. I created the /etc/.rs_sec file, on each line is a 'user:password' entry
(these users are independent of system users/passwords):
root:password
3. started the rsync in daemon mode
# /usr/bin/rsync --daemon
you can view the logfile /var/log/rsyncd.log for errors
On the DNS-323 192.168.1.11
1. modify the path (not sure if this is absolutely necessary)
# export PATH=/mnt/HD_a2/lnx_bin:$PATH
2. change to lnx_bin directory
# cd /mnt/HD_a2/lnx_bin
3. created the local directory
# mkdir /mnt/HD_a2/data
# chmod 777 /mnt/HD_a2/data
4. run the rsync command:
# rsync -av root@192.168.1.12::data /mnt/HD_a2/data
when rsync asks for root password I entered the text I put in the password part
(after the ':') of the /etc/.rs_sec file on the server. In my case I entered 'password'
Since the rysnc daemon user/password is independent of the system users, I did have some permission problems.
On the server Kurobox (as root), I fixed the permissions with the following commands
to make sure each file is readable by others
# find . -not -perm -o+r -exec chmod +r {} \;
to make sure each directory is readable by others
# find . -type d -exec chmod +rx {} \;
Offline