Re: remote copy file
- From: Günther Schwarz <strap@xxxxxx>
- Date: Sun, 16 Mar 2008 10:14:08 +0100
Ron Eggler wrote:
Nikos Chantziaras wrote:
Nikos Chantziaras wrote:I'm not sure if you understood my problem right. I have an embedded
[...]
As I understand it, you need the embedded device to initiate the
ransfer, not the remote PC
Err, the other way around. I meant "you need the remote PC to
initiate the transfer, not the embedded device."
device FROM which I need to send a file up to our central server.
rsync sounds good been looking into configuring it.
I put rsyncd on my "server" and it looks like:
You do not need rsyncd running on the embedded device, sshd is enough.
Just put a valid public key of an appropriate user on the little box
and use rsync on the server.
I do this every day as a crontab entry in order to copy backup files on
an Asus WL-HDD NAS called stupidlittlebox:
amanda@noname> rsync -av /Backup/amanda --rsh=ssh
stupidlittlebox:/tmp/harddisk/Backup/
Sshd on the box is dropbear. Note that I do have an user amanda on
stupidlittlebox. If not I would have to specify another user. And make
sure port 22 is not blocked by a packet filter on the embedded
device, 'nmap stupidlittlebox' ;-)
If your transfer is triggered on the remote side by something happening
on the box (intrusion detection, battery getting low, no more milk in
the fridge or such) why do not simply use smtp to notify the server
with a mail message?
Günther
.
- Follow-Ups:
- Re: remote copy file
- From: Ron Eggler
- Re: remote copy file
- References:
- remote copy file
- From: Ron Eggler
- Re: remote copy file
- From: Nikos Chantziaras
- Re: remote copy file
- From: Ron Eggler
- Re: remote copy file
- From: Nikos Chantziaras
- Re: remote copy file
- From: Nikos Chantziaras
- Re: remote copy file
- From: Ron Eggler
- remote copy file
- Prev by Date: Re: Dumb question of the week.
- Next by Date: Re: Dumb question of the week.
- Previous by thread: Re: remote copy file
- Next by thread: Re: remote copy file
- Index(es):
Relevant Pages
|