Hi,
I've created a patch that introduces new setting: rsync_user. Currently cobbler replicate would run 'rsync remote_server:...', so the user will be assumed to be 'root'. For "paswordless" replications this is not ideal, as making "paswordless" root account is generally not a good idea.
This setting allows specifying any user on the remote system, effectively changing rsync command to 'rsync user@remote_server:...'. If not specified it will not append anything.
Kind regards, Rytis
On Wed, Dec 9, 2009 at 8:12 AM, Rytis Sileika rytis.sileika@gmail.com wrote:
Hi,
I've created a patch that introduces new setting: rsync_user. Currently cobbler replicate would run 'rsync remote_server:...', so the user will be assumed to be 'root'. For "paswordless" replications this is not ideal, as making "paswordless" root account is generally not a good idea.
This setting allows specifying any user on the remote system, effectively changing rsync command to 'rsync user@remote_server:...'. If not specified it will not append anything.
The new cobbler (2.x) uses rsyncd for replication with the native rsync protocol I thought. Michael mentioned removing support for rsync over ssh due to key problems. You can control the user that is ran on the remote side by changing the rsyncd.conf template. Forgive my ignorance, but does cobbler 2.x support replication over rsync/ssh?
The new cobbler (2.x) uses rsyncd for replication with the native rsync protocol I thought. Michael mentioned removing support for rsync over ssh due to key problems. You can control the user that is ran on the remote side by changing the rsyncd.conf template. Forgive my ignorance, but does cobbler 2.x support replication over rsync/ssh?
I would have thought so, the piece of code that's responsible for syncing is still there...
Using native rsyncd will impose additional problems, like rsync port being blocked on firewalls, whereas SSH is usually open. I think rsync/ssh should remain available as an option.
On Wed, Dec 9, 2009 at 9:53 AM, Rytis Sileika rytis.sileika@gmail.com wrote:
The new cobbler (2.x) uses rsyncd for replication with the native rsync protocol I thought. Michael mentioned removing support for rsync over ssh due to key problems. You can control the user that is ran on the remote side by changing the rsyncd.conf template. Forgive my ignorance, but does cobbler 2.x support replication over rsync/ssh?
I would have thought so, the piece of code that's responsible for syncing is still there...
Using native rsyncd will impose additional problems, like rsync port being blocked on firewalls, whereas SSH is usually open. I think rsync/ssh should remain available as an option.
Well I was more curious if your code even works than anything else. Have you tested it? I've not tried replication with rsync over ssh and know that Michael actively wanted to deprecate it for 2.0. However I know that rsyncd is the preferred and most tested way for replication in cobbler 2.x.
The new cobbler (2.x) uses rsyncd for replication with the native rsync protocol I thought. Michael mentioned removing support for
rsync
over ssh due to key problems. You can control the user that is ran on the remote side by changing the rsyncd.conf template. Forgive my ignorance, but does cobbler 2.x support replication over rsync/ssh?
I would have thought so, the piece of code that's responsible for syncing is still there...
Using native rsyncd will impose additional problems, like rsync port being blocked on firewalls, whereas SSH is usually open. I think rsync/ssh should remain available as an option.
I agree with this, in an enterprise environment trying to get additional ports opened and through a change management process can be an undertaking .. :-/ I personally use rsync over sshd and never fuss with rsyncd due to the simplicity of it.
Curious to know why rsyncd would be prefer'd to rsync over ssh?
-- glenn - terremark
cobbler-devel@lists.fedorahosted.org