2009/9/29 Philippe Eveque philippe.eve...@gmail.com
2009/9/29 Michael DeHaan mdeh...@redhat.com
On 09/29/2009 03:24 AM, Philippe Eveque wrote:
2009/9/28 Michael DeHaan mdeh...@redhat.com
I noticed the following:
- on server2 set up from scratch
cobbler import was
2009/9/28 Michael DeHaan mdeh...@redhat.com
I noticed the following:
- on server2 set up from scratch
cobbler import was complaining that the issued rsync
command was failing
I had to disable selinux for rsync to make cobbler import working
with the following command.
On 09/29/2009 03:24 AM, Philippe Eveque wrote:
2009/9/28 Michael DeHaan mdeh...@redhat.com mailto:mdeh...@redhat.com
I noticed the following:
- on server2 set up from scratch
cobbler import was complaining that the issued rsync
command was failing
2009/9/29 Michael DeHaan mdeh...@redhat.com
On 09/29/2009 03:24 AM, Philippe Eveque wrote:
2009/9/28 Michael DeHaan mdeh...@redhat.com
I noticed the following:
- on server2 set up from scratch
cobbler import was complaining that the issued rsync
command was failing
Hi,
to share my testing experience with cobbler2.0 (thanks for it!) hoping it
can hepls others.
My context:
- having one cobbler server1 being migrated from 1.6.x to 2.0.
- having one cobbler server2 directly installed in 2.0
Both servers configured with ldap authentication in
I noticed the following:
- on server2 set up from scratch
cobbler import was complaining that the issued rsync
command was failing
I had to disable selinux for rsync to make cobbler import working
with the following command.
root# setsebool -P rsync_disable_trans=1
