> Seemed to be worthy of a blog
>
> http://danwalsh.livejournal.com/61646.html
Thanks, Dan - the "unconfined domain" method is the ticket!
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2013 10:41 AM, m.r...@5-cent.us wrote:
> lheck...@users.sourceforge.net wrote:
>>
>>> I use rsync extensively to transfer entire systems from and to SElinux
>>> enforcing environments and have never had a problem with reads using
>>> rsync
lheck...@users.sourceforge.net wrote:
>
>> I use rsync extensively to transfer entire systems from and to SElinux
>> enforcing environments and have never had a problem with reads using
>> rsync when logged on as the root user. My typical command line is
>> some variation of the following:
>>
>> /
> I would try the booleans
>
> getsebool -a | grep rsync
Yes, I've set rsync_client. The others aren't relevant here IMHO.
allow_rsync_anon_write --> on
rsync_client --> on
rsync_export_all_ro --> off
rsync_use_cifs --> off
rsync_use_nfs --> off
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2013 08:26 AM, Gordon Messmer wrote:
> On 01/07/2013 03:59 AM, lheck...@users.sourceforge.net wrote:
>> Big mistake. Most or all services with config files under /etc could no
>> longer read their config files, including ssh. It looks like the
> I use rsync extensively to transfer entire systems from and to SElinux
> enforcing environments and have never had a problem with reads using
> rsync when logged on as the root user. My typical command line is
> some variation of the following:
>
> /usr/bin/rsync -avX --delete-after -
On Mon, January 7, 2013 06:59, lheck...@users.sourceforge.net wrote:
> I'm trying to use rysnc to back up some directories on a CentOS6
> machine that uses selinux in enforcing mode. Most files didn't
> transfer, so I tried the example from rsync_selinux(8):
>
>Allow rsync servers to read
On 01/07/2013 03:59 AM, lheck...@users.sourceforge.net wrote:
> Big mistake. Most or all services with config files under /etc could
> no longer read their config files, including ssh. It looks like the selinux
> type was substituted rather than added? Thankfully, I was able to recover.
Yes,
I'm trying to use rysnc to back up some directories on a CentOS6 machine
that uses selinux in enforcing mode. Most files didn't transfer, so I tried
the example from rsync_selinux(8):
Allow rsync servers to read the /var/rsync directory by adding the pub-
lic_content_t file type to t
9 matches
Mail list logo
