I've found some more info here:

https://www.mail-archive.com/[email protected]/msg32328.html

On 21/01/19 7:33 PM, Richard Hector wrote:
> On 21/01/19 7:12 PM, Sean Whitney wrote:
>> hmm, I'm not sure I got all of that.
>>
>> My understanding is the string starting -vlHog is all single item 
>> arguments to rsync.
> 
> Mine too. And most of them (the first ones) are the same as one uses on
> the client side, and are documented in the man page. The 'e', though,
> doesn't really make sense for the 'e' in the man page, and the rest make
> even less, so I assume the 'e' (or maybe 'e.') introduces the special
> ones for the server end.
> 
>>  I can't remember where i got it from, it might have 
>> been with a sshd debug statement.
> 
> I can't remember where I originally got it either; either from an sshd
> debug like you, or from the SSH_ORIGINAL_COMMAND that is made available
> to forced commands.
> 
>>  I don't think dirvish is going to 
>> change those arguments any time soon.
> 
> The trouble is, I think it already has. Well, maybe not dirvish - maybe
> rsync. When I first set this up ages ago, I put in far fewer options
> than are there now.
> 
>> For remote hosts I set xdev to 0 in the dirvish default.conf file and 
>> backup everything, and set excludes for parts of the filesystem I don't 
>> want.
> 
> Mostly I'm backing up VPSes that are all on one filesystem, so xdev
> wouldn't help (though I think I use it out of habit). And excludes are
> easy enough. But how do you do a separate backup of the bits you've
> excluded? The only way I've found, when using forced commands, is to use
> a different key with a different forced command. My wrapper solves that.
> 
> There are a few reasons for wanting more than one backup from the same
> machine. Some of my backups are now too big for one rsync to cope with -
> it runs out of RAM keeping track of the file list and duplicates. And
> it's nice keeping them on different filesystems on the backup server,
> because then I can use df to keep track of the size, which is much, much
> faster than du which I'd need for partial filesystems.
> 
> Cheers,
> Richard
> 
>>
>> Sean
>>
>> On 1/20/19 8:38 PM, Richard Hector wrote:
>>> On 21/01/19 8:31 AM, Sean Whitney wrote:
>>>> Richard:
>>>>
>>>> I'm not sure what you are attempting.  However, I allow root ssh access
>>>> to my remote servers from my dirvish server and the forced command
>>>> string is in the .ssh/authorized_keys file.  It looks like this
>>>>
>>>> from="<ip of dirvish server",command="rsync --server --sender
>>>> -vlHogDtpre.iL --numeric-ids .
>>>> /",no-port-forwarding,no-X11-forwarding,no-agent-forwarding ssh-dss <key
>>>> follows>
>>>
>>> Thanks Sean,
>>>
>>> Mine used to have:
>>>
>>> command="rsync --server --sender -vlHogDtprx --numeric-ids . /"
>>>
>>> ... as well as other options.
>>>
>>> Looking now at what the client requests, the mess of letters in the
>>> middle is now:
>>>
>>> -vlHogDtprxe.iLsfxC
>>>
>>> The trouble is, I can only look those up as far as the first x. After
>>> that, I have no idea what 'e.iLsfxC' actually means, which means I don't
>>> know when it might change. Actually, I don't really know if the previous
>>> options mean the same things as in a normal invocation either.
>>>
>>> At the moment, my wrapper script captures the whole block from the
>>> SSH_FORCED_COMMAND environment variable, and replays it (having checked
>>> that the final path component is acceptable).
>>>
>>> The goal, by the way, is to be able to backup multiple different paths
>>> on the same machine, with forced commands, and without having to ahve a
>>> different key for each path (which is what I've been doing up till now).
>>>
>>> Thanks,
>>> Richard
>>>
>>>>
>>>>
>>>> Sean
>>>>
>>>> On 1/20/19 12:20 AM, Richard Hector wrote:
>>>>> Hi all,
>>>>>
>>>>> I'm writing a wrapper script to use as an ssh forced command.
>>>>>
>>>>> It would be useful to understand the options used in the "rsync --server
>>>>> --sender" command executed on the remote - but the man page doesn't
>>>>> cover them.
>>>>>
>>>>> Anyone know where to find such documentation?
>>>>>
>>>>> Cheers,
>>>>> Richard
>>>>> _______________________________________________
>>>>> Dirvish mailing list
>>>>> [email protected]
>>>>> http://www.dirvish.org/mailman/listinfo/dirvish
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Dirvish mailing list
>>> [email protected]
>>> http://www.dirvish.org/mailman/listinfo/dirvish
>>>
>>
> 
> _______________________________________________
> Dirvish mailing list
> [email protected]
> http://www.dirvish.org/mailman/listinfo/dirvish
> 

_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish

Reply via email to