Hi
I have a disk which two of the partitions are part of a RAID1 setup. I'm
trying to rename the the second raided partition
mdadm -E /dev/sdc4
/dev/sdc4:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 83d7657b:ebfddcb7:36b0fa14:d29a350c
Name :
On 10/18/2016 03:28 PM, Clint Dilks wrote:
So first
question is are people generally modifying the list of ciphers supported by
the ssh client and sshd?
I suspect that "generally" people are not. I do, because I can, and so
that I can offer at least some advice to people who aim to do so.
On CentOS 7 I put the following at the end of ssh
KexAlgorithms
curve25519-sha...@libssh.org,diffie-hellman-group-exchange-sha256
I believe that prevents the CBC ciphers from being used.
CentOS 6 I *think* does not support curve25519 so that one may not be an
option for CentOS 6. That really
Hi,
In a recent security review some systems I manage were flagged due to
supporting "weak" ciphers, specifically the ones listed below. So first
question is are people generally modifying the list of ciphers supported by
the ssh client and sshd?
On CentOS 6 currently it looks like if I remove a
Dear Centos Users
We are running centos on our HPC.
Indeed, we have a problem with running some software using X11 server such
as pymol. For your information, we are using cygwin to access to the
hpc (using ssh -X -Y usern...@xxx.xxx.xxx.xxx)
When we are testing glxinfo on my desktop, it gives us t
On 10/18/2016 12:32 PM, Leroy Tennison wrote:
-> Is there a way to get a date stamp for the dmesg?
At least on CentOS7: dmesg -T
yeah, thats new to el7 ...
--
john r pierce, recycling bits in santa cruz
___
CentOS mailing list
CentOS@centos.org
ht
-> Is there a way to get a date stamp for the dmesg?
At least on CentOS7: dmesg -T
- Original Message -
From: "Dan Hyatt"
To: "CentOS mailing list"
Sent: Tuesday, October 18, 2016 1:36:46 PM
Subject: [CentOS] Lockd: failed to reclaim lock for pid ...
My environment is "heterogeneous" m
My environment is "heterogeneous" my authentication and home server are
currently stuck on a 1G shared network, the production servers and
storage servers are on a bonded 40G network, all are in the same VLAN. I
have about 100 servers on the 40GB bonded network each with 12cores and
128GB of me
On 10/18/2016 12:10 AM, Barry Brimer wrote:
I tried creating /etc/modprobe.d/blacklist with the following :
blacklist snd_hda_intel
blacklist snd_hda_codec_hdmi
That didn't work.
I doubt this is it, but it is easy to test. For some reason I thought that
anything in modprobe.d had to end
>I tried creating /etc/modprobe.d/blacklist with the following :
>
>blacklist snd_hda_intel
>blacklist snd_hda_codec_hdmi
>
>That didn't work.
>
I doubt this is it, but it is easy to test. For some reason I thought that
anything in modprobe.d had to end in .conf to be processed. I could be wron
10 matches
Mail list logo