[CentOS] Standard Dracut configuration file /etc/dracut.conf

Hi Centos Experts, I want to have hands on /etc/dracut.conf file which standard centos 7.3 is using to create initrd.img present in the DVD ISO : /isolinux/initrd.img >From where can i get /etc/dracut.conf, so that i can create exact replica of initrd.img which centos 7.3 is sending in DVD ISO.

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

On 2017-01-20, Valeri Galtsev wrote: > > Hm, not certain what process you describe. Most of my controllers are > 3ware and LSI, I just pull failed drive (and I know phailed physical drive > number), put good in its place and rebuild stars right away. I know for sure

Re: [CentOS] amanda and selinux

On Fri, Jan 20, 2017 at 08:29:29PM -0500, John Jasen wrote: > There's an option to get selinux to report on all the 'don't audit' > bits, which can be toggled on and off as needed. This may help in debugging. Yes, "sesearch -D". And there are several dealing with amanda, mostly about recovery

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

I was just trying to be helpful. *backs away slowly* Cameron On Fri, Jan 20, 2017 at 5:16 PM, Valeri Galtsev wrote: > > On Fri, January 20, 2017 7:00 pm, Cameron Smith wrote: > > Hi Valeri, > > > > > > Before you pull a drive you should check to make sure that doing

Re: [CentOS] amanda and selinux

There's an option to get selinux to report on all the 'don't audit' bits, which can be toggled on and off as needed. This may help in debugging. On 01/19/2017 06:25 PM, Jon LaBadie wrote: > Anyone familiar with the selinux policy for the > amanda backup software package? I'm getting lots > of

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

On Fri, January 20, 2017 7:00 pm, Cameron Smith wrote: > Hi Valeri, > > > Before you pull a drive you should check to make sure that doing so > won't kill the whole array. Wow! What did I say to make you treat me as an ultimate idiot!? ;-) All my comments, at least in my own reading, we about

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

Hi Valeri, Before you pull a drive you should check to make sure that doing so won't kill the whole array. MegaCli can help you prevent a storage disaster and can let you have more insight into your RAID and the status of the virtual disks and the disks than make up each array. MegaCli will

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

On 01/20/2017 09:31 AM, Peter Peltonen wrote: I am planning to have RAID1 setup and I am wondering if I should use the controller's RAID functionality which has 2GB cache or should I go with JBOD + Linux software RAID? I'd recommend testing the specific application that will run on this

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

On 1/20/2017 10:59 AM, Joseph L. Casale wrote: Not related to your question, but something to keep in mind: What type of enclosure are you using? If you are using an engineered system your enclosure will communicate with the controller. When a disk fails it's a pain in the arse to figure out

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

On Fri, January 20, 2017 5:16 pm, Joseph L. Casale wrote: >> This is why before configuring and installing everything you may want to >> attach drives one at a time, and upon boot take a note which physical >> drive number the controller has for that drive, and definitely label it >> so >> y9ou

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

On 1/20/2017 9:31 AM, Peter Peltonen wrote: I am planning to have RAID1 setup and I am wondering if I should use the controller's RAID functionality which has 2GB cache or should I go with JBOD + Linux software RAID? The disks I am going to use are 6TB Seagate Enterprise ST6000NM0034 7200rpm

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

> This is why before configuring and installing everything you may want to > attach drives one at a time, and upon boot take a note which physical > drive number the controller has for that drive, and definitely label it so > y9ou will know which drive to pull when drive failure is reported.

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

On Fri, January 20, 2017 12:59 pm, Joseph L. Casale wrote: >> The disks I am going to use are 6TB Seagate Enterprise ST6000NM0034 >> 7200rpm SAS/12Gbit 128 MB > > Sorry to hear that, my experience is the Seagate brand has the shortest > MTBF > of any disk I have ever used... > >> If hardware RAID

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

> The disks I am going to use are 6TB Seagate Enterprise ST6000NM0034 > 7200rpm SAS/12Gbit 128 MB Sorry to hear that, my experience is the Seagate brand has the shortest MTBF of any disk I have ever used... > If hardware RAID is preferred, the controller's cache could be updated > to 4GB and I

Re: [CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

Haven't used Areca in a very long time, but with raid controllers the rule is to use it in order to take advantage of the cache. The performance gains will be more than significant, especially for writes. hth -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -

[CentOS] CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?

Hi, Does anyone have experiences about ARC-1883I SAS controller with CentOS7? I am planning to have RAID1 setup and I am wondering if I should use the controller's RAID functionality which has 2GB cache or should I go with JBOD + Linux software RAID? The disks I am going to use are 6TB Seagate

[CentOS] Can/should I mix entropy sources?

I've got 2 sources of entropy in my CentOS7 system, a hardware RNG and the Intel rdrand instruction. Is it advisable to just use a single source or can/should I mix the 2 sources? If I mix the 2 sources how is it done? Presumably I could use the rngd service to handle the Intel source, but

[CentOS] koji in extras older than epel

Now that EPEL 7 has koji-1.11, should the one in CentOS 7 extras be updated or removed? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SSSD cache case-sensitivity

On 20-01-17 16:35, Gordon Messmer wrote: I find filing bug reports generally more effective than hoping, and submitting patches more effective still. I did already file a bug report. Since this involves a change in definition I'll wait for input before starting on a patch. ;-) -- Robbert

Re: [CentOS] CentOS 7 httpd cgi script file not able to write to /tmp

Something (possibly systemd) creates per user / per process (?) /tmp directories. These are actually held in /tmp/systemd-private-* Gary On Friday 20 January 2017 15:19:52 Jerry Geis wrote: > Fun fact... If I echo my data to the same directory as the script is > located in it works. But it

Re: [CentOS] SSSD cache case-sensitivity

On 01/20/2017 04:13 AM, Robbert Eggermont wrote: Since this (opposite defaults) is broken by design, I hope the AD provider will be fixed so it follows the general default. I find filing bug reports generally more effective than hoping, and submitting patches more effective still.

Re: [CentOS] CentOS 7 httpd cgi script file not able to write to /tmp

The behavior you describe should be normal for any web server, as it is for Apache, which is what I use. It is a security feature that prevents malicious attacks on a web server from writing malware anywhere else in the filesystem and possibly gaining elevated privileges. On 01/20/2017 10:19

Re: [CentOS] CentOS 7 httpd cgi script file not able to write to /tmp

Fun fact... If I echo my data to the same directory as the script is located in it works. But it does not allow writing to /tmp I'm good with that. Thanks, Jerry On Fri, Jan 20, 2017 at 9:54 AM, Jerry Geis wrote: > Hi - Thanks for the reply. > > I actually have selinux

Re: [CentOS] CentOS 7 httpd cgi script file not able to write to /tmp

Hi - Thanks for the reply. I actually have selinux disabled on this box. Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7 httpd cgi script file not able to write to /tmp

Just a speculation but /tmp is usually world-writable which leads me to suspect SELinux (or AppArmor with other distros.) - Original Message - From: "Jerry Geis" To: "CentOS mailing list" Sent: Friday, January 20, 2017 7:29:02 AM Subject:

[CentOS] CentOS 7 httpd cgi script file not able to write to /tmp

Hi all, I have a script running in httpd. The script runs fine. However I want to "echo" some debug information into a file. The file is never created. Is there some security thing that has to be enable/disabled to allow a script in httpd to write to a file? Thanks, Jerry

Re: [CentOS] SSSD cache case-sensitivity

Hi John, Thanks for pointing me to case_sensitive, that indeed is the cause: the default for "case_sensitive" is "True", but for the AD provider "True" is invalid(??), so it defaults to "False"(???)! Good news is that with both "case_sensitive = False" and "case_sensitive = Preserving" the

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

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] SSSD cache case-sensitivity

On Fri, 20 Jan 2017, Robbert Eggermont wrote: Dear all, I'm running CentOS 7.3 with SSSD. I'm using sssd-ad to talk to an AD backend. Group names in the AD contain capitals. When sssd-ad is working normally, group names returned are all lowercase. However, when the AD backend goes offline,

[CentOS] SSSD cache case-sensitivity

Dear all, I'm running CentOS 7.3 with SSSD. I'm using sssd-ad to talk to an AD backend. Group names in the AD contain capitals. When sssd-ad is working normally, group names returned are all lowercase. However, when the AD backend goes offline, group names returned from the SSSD cache