[CentOS] selinux & rsyncd: Allowing global read for backup

I want to set up rsyncd to expose the whole drive read-only to BackupPC running on another machine. So I need to set selinux to allow this. According to the Fedora wiki I can do so like this: setsebool -P rsync_disable_trans 1 But when I run the

[CentOS] Amavis on Centosl help

I'm moving from Ubuntu to CentOS 7 Previously, on Ubuntu, installing amavisd would lead to etc/amavis/conf.d that contained: 01-debian 05-domain_id 05-node_id 15-av_scanners 15-content_filter_mode 20-debian_defaults 21-ubuntu_defaults 25-amavis_helpers 30-template_localization

[CentOS] CentOS-announce Digest, Vol 143, Issue 2

Send CentOS-announce mailing list submissions to centos-annou...@centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to

Re: [CentOS] selinux & rsyncd: Allowing global read for backup

More digging and "getsebool -a | grep rsync" revealed the rsync_export_all_ro bool. I set that and now it looks like I can rsync from my BackupPC system. setsebool -P rsync_export_all_ro 1 ___ CentOS

Re: [CentOS] Amavis on Centosl help

Hi Barbara, Thank you for that, very useful. So, if I'm not mistaken, it sounds like the underlying suggestion is that I could just delete /etc/amavisd/amavisd.conf and replace it with a the contents of /etc/amavis/conf.d/ from elsewhere. Tim On 4 January 2017 at 13:24, Barbara Krašovec

Re: [CentOS] Amavis on Centosl help

I'm forwarding the answer from my colleague: release notes: - provide two new subroutines available for calling from config files: include_config_files() and include_optional_config_files(), each take a list of filenames as arguments, and reads & evaluates them just like normal

Re: [CentOS] ghostscript update breaks evince

On 01/04/2017 04:49 PM, David C. Miller wrote: - Original Message - From: "Robert Nichols" To: centos@centos.org Sent: Wednesday, January 4, 2017 12:21:48 PM Subject: [CentOS] ghostscript update breaks evince Today's ghostscript.x86_64 0:8.70-21.el6_8.1

Re: [CentOS] Issue with MariaDB-server

On 01/04/2017 01:46 PM, Clint Dilks wrote: My own research suggests this is reasonably safe, but does anyone see a reason why this shouldn't be used ? Not really, but if you start this with systemd, using the service file Red Hat distributes, then it isn't necessary because systemd will have

Re: [CentOS] Issue with MariaDB-server

On Thu, Jan 5, 2017 at 4:01 PM, Gordon Messmer wrote: > On 01/04/2017 01:46 PM, Clint Dilks wrote: > >> My own research suggests this is reasonably safe, but does anyone see a >> reason why this shouldn't be used ? >> > > > Not really, but if you start this with

Re: [CentOS] [OT] Network Attached Storage

On Jan 4, 2017 6:31 PM, "TE Dukes" wrote: > -Original Message- > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of John R > Pierce > Sent: Tuesday, January 3, 2017 1:50 PM > To: centos@centos.org > Subject: Re: [CentOS] [OT] Network Attached

Re: [CentOS] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK

> On Jan 3, 2017, at 2:59 PM, lakhera2017 wrote: > > |- 1:0:0:15 sdq 65:0 failed ready running > - 3:0:0:15 sdai 66:32 failed ready running Does the same SAN target fail each time? What brand/model/firmware SAN switch is between initiator and target? Does the HBA

Re: [CentOS] ghostscript update breaks evince

- Original Message - > From: "Robert Nichols" > To: centos@centos.org > Sent: Wednesday, January 4, 2017 12:21:48 PM > Subject: [CentOS] ghostscript update breaks evince > Today's ghostscript.x86_64 0:8.70-21.el6_8.1 update causes evince to refuse to >

Re: [CentOS] [OT] Network Attached Storage

> -Original Message- > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of John R > Pierce > Sent: Tuesday, January 3, 2017 1:50 PM > To: centos@centos.org > Subject: Re: [CentOS] [OT] Network Attached Storage > > I've been using a HP Microserver for the last couple years as my

[CentOS] Re: ghostscript update breaks evince

On Thu, 5 Jan 2017 03:40, Robert Nichols wrote: On 01/04/2017 04:49 PM, David C. Miller wrote: - Original Message - > From: "Robert Nichols" > To: centos@centos.org > Sent: Wednesday, January 4, 2017 12:21:48 PM > Subject: [CentOS] ghostscript update breaks evince > Today's

Re: [CentOS] [OT] Network Attached Storage

> -Original Message- > From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Tom > Bishop > Sent: Wednesday, January 4, 2017 8:23 PM > To: CentOS mailing list > Subject: Re: [CentOS] [OT] Network Attached Storage > > On Jan 4, 2017 6:31 PM, "TE Dukes"

Re: [CentOS] 7.3: Gnome workspaces mirrored

On 04/01/17 22:09, Gerhard Schneider wrote: An user is using 2 displays and configured Gnome to "Static Workspaces only on primary display on" using gnome-tweak-tool Till 7.2 it was working as expected. After upgrading to 7.3 the content on the primary screen gets mirrored to all workspaces.

Re: [CentOS] yum update pulls in lvm-cluster on 7.3

On Wed, Jan 4, 2017 at 6:30 AM, wrote: > Hi, > > Sorry for the delayed response. No problem > Hummm, According to the changelog your version of lvm2 is over a year old. > Yes, it was a test vm server not recently updated. > > So I guess what I am trying to figure out is

[CentOS] 7.3: Gnome workspaces mirrored

An user is using 2 displays and configured Gnome to "Static Workspaces only on primary display on" using gnome-tweak-tool Till 7.2 it was working as expected. After upgrading to 7.3 the content on the primary screen gets mirrored to all workspaces. When switching to "Static Workspaces only on

Re: [CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

On Wed, 4 Jan 2017, Locane wrote: Still though - someone manages the default repositories - so my question is, who decides when a package gets an update from whatever CentOS ships with default to a newer version? How does that process take place, and, can I affect it by adding

Re: [CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

Thanks for the breakdown Paul - I've had to learn all my sysadmin stuff through organic interactions like this. Still though - someone manages the default repositories - so my question is, who decides when a package gets an update from whatever CentOS ships with default to a newer version? How

Re: [CentOS] yum update pulls in lvm-cluster on 7

On Wed, 4 Jan 2017, Peter Kjellström wrote: On Tue, 13 Dec 2016 08:16:06 -0500 (EST) m...@tdiehl.org wrote: I ran "yum update" this morning on a 7.2 machine with all of the cr updates applied to it and yum wants to install lvm-cluster and a bunch of deps. ...

Re: [CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

On Wed, 4 Jan 2017, Locane wrote: My questions are, who decides what packages are current for CentOS when I "yum upgrade"? That's determined by the repositories defined and enabled in /etc/yum.conf and /etc/yum.repos.d/*.repo. To see the repositories enabled by your system, ask yum: yum

[CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

Hello all! I'm brand new to the mailing list, and I've encountered an issue with the microcode_ctl package version 2.1-16 being installed during the CentOS 7.3 upgrade. It causes my servers to hard stop and they need to be forcibly powered off and back on again with the power button to continue.

Re: [CentOS] Strange (?) device.map in CentOS 7 VM installations

On 01/04/2017 03:07 AM, Nikolaos Milas wrote: Is it normal in CentOS 7 to have a device map with two entries esp. when the (physical or virtual) hardware has only one hd ? I don't see that on VMs that I manage. Some of the physical machines that I manage do have duplicates in the

Re: [CentOS] yum update pulls in lvm-cluster on 7.3

On Tue, 13 Dec 2016 08:16:06 -0500 (EST) m...@tdiehl.org wrote: > I ran "yum update" this morning on a 7.2 machine with all of the cr > updates applied to it and yum wants to install lvm-cluster and a > bunch of deps. ... > == >

Re: [CentOS] Strange (?) device.map in CentOS 7 VM installations

On 29/12/2016 11:24 πμ, Nikolaos Milas wrote: ...I have found that all my CentOS 7 installations (VMs under KVM) have the same /boot/grub2/device.map, which seemingly refers to two HDs, although the VMs in fact include only one (virtual) HD. ... This is NOT the case with my CentOS 5 and

Re: [CentOS] ghostscript update breaks evince

On Wed, Jan 4, 2017 at 3:21 PM, Robert Nichols wrote: > Today's ghostscript.x86_64 0:8.70-21.el6_8.1 update causes evince to > refuse to > display any postscript file. Running evince from a terminal session, I see > the > errors: > > invalidaccess -7 > invalidaccess

[CentOS] ghostscript update breaks evince

Today's ghostscript.x86_64 0:8.70-21.el6_8.1 update causes evince to refuse to display any postscript file. Running evince from a terminal session, I see the errors: invalidaccess -7 invalidaccess -7 invalidaccess -7 ** (evince:1252): WARNING **: Error rendering thumbnail Downgrading to

Re: [CentOS] ghostscript update breaks evince

Yes, it looks like evince is not working for .ps files on my system running fully up to date CentOS 6.8. Three years ago, a .pdf version of this file was created and it still displays as it should using evince. [user@computer Documents]$ evince DPS_2014_1443inv.ps & [1] 9865 [user@computer

[CentOS] Firefox Issue

Everyone is back at work and starting to use computers on our smallest network which has Internet access through a rather old Linksys router.  Two systems were left on and screen-locked over the extra long weekend.  There does not appear to have been any Internet access interruption in our

Re: [CentOS] Firefox Issue

> Instead, a site located at the link https://gaibacoupontec.com > was displayed with a message indicating that there was an urgent > Firefox update required. Have you checked the user's Firefox profile for any unusual extensions? That would be my first suspicion.

[CentOS] Issue with MariaDB-server

Hi, Today I have updated a CentOS 6.8 system that has MariaDB-server installed from http://yum.mariadb.org/5.5/centos6-amd64 and found that I had an SELinux issue. I know this is not really CentOS related, but thought I would check if anyone else on this list uses this repository and has also

[CentOS-announce] Release for CentOS 7.3.1611 on ARM64/AArch64

I am pleased to announce the general availability of CentOS Linux 7 (1611) for AArch64/ARM64 machines. == Changes The kernel has been rebased from 4.2.0 to 4.5.0, and includes several patches recently merged into the upstream. The kernel patches and modifications can be found at

[CentOS-announce] CESA-2017:0013 Moderate CentOS 7 ghostscript Security Update

CentOS Errata and Security Advisory 2017:0013 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0013.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64:

[CentOS-announce] CESA-2017:0014 Moderate CentOS 6 ghostscript Security Update

CentOS Errata and Security Advisory 2017:0014 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0014.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: