Look at the "sshfs" command as you would at the "mount" command:
mount /some/device /some/path 

sshfs doesn't "mount" devices, it "mount(s)" remote directories: 

So:
>> rsync -avHp /home/joe/mydata/upquick/ vsiq@box5.bluehost.com:www/upquick/
Could translate to: 

mkdir -p /remote/www/upquick
sshfs vsiq@box5.bluehost.com:www/upquick /remote/www/upquick
rsync -avHp /home/joe/mydata/upquick/ /remote/www/upquick
Clear as mud?   :)
ET 

 

joe@actionline.com writes: 

> 
>> One way to "provide the password once per connection" is using sshfs: 
>>
>> sshfs user@remotehost:/path/I/care /where/I/want/it 
>>
>> Give your password and the mount will persist until either machine is
>> booted or the connection dies. 
>>
>> Now you can:
>> rsync -[all I want] /path/to/save/ /where/I/want/it
> 
> Thanks ET. While I plan to try to set up the key based authentication that
> Bryan explained, this sshfs looks like a good alternative. However, I
> don't quite understand the sshfs example, especially the "/path/I/care"
> part and all the rest that should follow on the sshfs line. How would I do
> that in the example that I originally provided? 
> 
> # update.blue 
> 
> sshfs (what goes here?):/(what goes here?)/ (what goes here?) 
> 
> rsync -avHp --progress /home/joe/mydata/upquick/
> vsiq@box5.bluehost.com:www/upquick/ 
> 
> rsync -avHp --progress /home/joe/mydata/zip/ vsiq@box5.bluehost.com:www/zip/ 
> 
> rsync -avHp --progress /home/joe/mydata/av7/ vsiq@box5.bluehost.com:www/av7/ 
> 
>  
> 
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss