On Mon, May 23, 2016 at 3:09 PM, Jerry Geis wrote:
> When I run this command:
> rm /tmp/jerry.txt
> rm: remove regular file â/tmp/jerry.txtâ?
>
> I get the a with the carrot on top...
>
> How do I get back to the normal characters ?
>
> echo $TERM
> linux
>
> Thanks,
>
>
On 05/25/2016 06:43 PM, Always Learning wrote:
>
> On Wed, 2016-05-25 at 22:32 +0100, Timothy Murphy wrote:
>
>> Also, yum had associations which it was sad to lose.
>
> Perhaps the Fedora ("We love consulting all affected users") replacement
> could be named MUD.
>
> Now we await the System-D
On Wed, 2016-05-25 at 22:32 +0100, Timothy Murphy wrote:
> Also, yum had associations which it was sad to lose.
Perhaps the Fedora ("We love consulting all affected users") replacement
could be named MUD.
Now we await the System-D controlling interface ;-)
--
Regards,
Paul.
England, EU.
On 05/25/16 16:38, Timothy Murphy wrote:
Kenneth Porter wrote:
I saw mention of dnf in a blog article about installing a package on
CentOS. Further investigation revealed that Fedora is replacing yum with
dnf, apparently a new and better yum. But it wasn't clear if dnf was a
For the normal
On 2016-05-25 19:13, Kelly Lesperance wrote:
> Hdparm didn’t get far:
>
> [root@r1k1 ~] # hdparm -tT /dev/sda
>
> /dev/sda:
> Timing cached reads: Alarm clock
> [root@r1k1 ~] #
Hi Kelly,
Try running 'iostat -xdmc 1'. Look for a single drive that has
substantially greater await than ~10msec.
Kenneth Porter wrote:
> I saw mention of dnf in a blog article about installing a package on
> CentOS. Further investigation revealed that Fedora is replacing yum with
> dnf, apparently a new and better yum. But it wasn't clear if dnf was a
For the normal user (like me) dnf is neither better nor
Kelly Lesperance wrote:
> Already done – they’re not being very helpful, as we don’t have a support
> contract, just standard warranty.
>
Right. We get support for five years, but then we keep things well past
that, we don't get rid of them till they're dying. (Don't talk to me about
"wasting tax
I should rephrase that – some parts of HP are helping us, but the team I opened
the case with isn’t being very helpful.
On 2016-05-25, 4:29 PM, "Kelly Lesperance" wrote:
>Already done – they’re not being very helpful, as we don’t have a support
>contract, just
Already done – they’re not being very helpful, as we don’t have a support
contract, just standard warranty.
On 2016-05-25, 4:27 PM, "centos-boun...@centos.org on behalf of
m.r...@5-cent.us"
wrote:
>Kelly Lesperance wrote:
>>
Kelly Lesperance wrote:
> LSI/Avago’s web pages don’t have any downloads for the SAS2308, so I think
> I’m out of luck wrt MegaRAID.
>
> Bounced the node, confirmed MPT Firmware 15.10.09.00-IT.
> HP Driver is v 15.10.04.00.
>
> Both are the latest from HP.
>
> Unsure why, but the module itself
LSI/Avago’s web pages don’t have any downloads for the SAS2308, so I think I’m
out of luck wrt MegaRAID.
Bounced the node, confirmed MPT Firmware 15.10.09.00-IT.
HP Driver is v 15.10.04.00.
Both are the latest from HP.
Unsure why, but the module itself reports version 20.100.00.00:
[root@r1k1
On 05/25/2016 12:38 PM, Kenneth Porter wrote:
But it wasn't clear if dnf was a drop-in replacement or if some
migration setup was required.
For users, it's a drop-in replacement. If you write extensions, some
migration is required, because the API has been cleaned up.
Is it supposed to
I saw mention of dnf in a blog article about installing a package on
CentOS. Further investigation revealed that Fedora is replacing yum with
dnf, apparently a new and better yum. But it wasn't clear if dnf was a
drop-in replacement or if some migration setup was required. Is it supposed
to
I installed the latest firmware and driver (mpt2sas) from HP on one system.
The driver is v20, it appears the firmware may be 15, though:
[ 11.128979] mpt2sas version 20.100.00.00 loaded
[ 11.513836] mpt2sas0: LSISAS2308: FWVersion(15.10.09.00),
ChipRevision(0x05), BiosVersion(07.39.00.00)
John R Pierce wrote:
> On 5/25/2016 11:44 AM, Kelly Lesperance wrote:
>> The HBA is an HP H220.
>
> OH.its a very good idea to verify the driver is at the same revision
> level as the firmware.not 100% sure how you do this under CentOS, my
> H220 system is running FreeBSD, and is at
Hdparm didn’t get far:
[root@r1k1 ~] # hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: Alarm clock
[root@r1k1 ~] #
On 2016-05-25, 2:44 PM, "Kelly Lesperance" wrote:
>The HBA is an HP H220.
>
>We haven’t really benchmarked individual drives – all 12 drives are
On 5/25/2016 11:44 AM, Kelly Lesperance wrote:
The HBA is an HP H220.
OH.its a very good idea to verify the driver is at the same revision
level as the firmware.not 100% sure how you do this under CentOS, my
H220 system is running FreeBSD, and is at revision P20, both firmware
and
On 5/25/2016 11:44 AM, Kelly Lesperance wrote:
The HBA is an HP H220.
for the uninitated, thats a LSI SAS2308, in IT (initiator-terminator) mode.
--
john r pierce, recycling bits in santa cruz
___
CentOS mailing list
CentOS@centos.org
The HBA is an HP H220.
We haven’t really benchmarked individual drives – all 12 drives are utilized in
one RAID-10 array, I’m unsure how we would test individual drives without
breaking the array.
Trying ‘hdparm -tT /dev/sda’ now – it’s been running for 25 minutes so far…
Kelly
On
What is the HBA the drives are attached to?
Have you done a quick benchmark on a single disk to check if this is a
raid problem or further down the stack?
Regards,
Dennis
On 25.05.2016 19:26, Kelly Lesperance wrote:
> [merging]
>
> The HBA the drives are attached to has no configuration that
Kelly Lesperance wrote:
> I’ve posted this on the forums at
> https://www.centos.org/forums/viewtopic.php?f=47=57926=244614#p244614
> - posting to the list in the hopes of getting more eyeballs on it.
>
> We have a cluster of 23 HP DL380p Gen8 hosts running Kafka. Basic specs:
>
> 2x E5-2650
> 128
[merging]
The HBA the drives are attached to has no configuration that I’m aware of. We
would have had to accidentally change 23 of them ☺
Thanks,
Kelly
On 2016-05-25, 1:25 PM, "Kelly Lesperance" wrote:
>They are:
>
>[root@r1k1 ~] # hdparm -I /dev/sda
>
They are:
[root@r1k1 ~] # hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: MB4000GCWDC
Serial Number: S1Z06RW9
Firmware Revision: HPGD
Transport: Serial, SATA Rev 3.0
Kelly Lesperance wrote:
> I’ve posted this on the forums at
> https://www.centos.org/forums/viewtopic.php?f=47=57926=244614#p244614
> - posting to the list in the hopes of getting more eyeballs on it.
>
> We have a cluster of 23 HP DL380p Gen8 hosts running Kafka. Basic specs:
>
> 2x E5-2650
> 128
Estimados,
Muy buenas tardes desde #CHILE,me comunico con ustedes debido a que en ciertas
oportunidades de envíos de correo, utilizando postfix, el sistema me devuelve
el correo con el mensaje "500 Line too long" (entre servidores que administro).
Desde el lado del log, aparece lo siguiente:
I’ve posted this on the forums at
https://www.centos.org/forums/viewtopic.php?f=47=57926=244614#p244614 -
posting to the list in the hopes of getting more eyeballs on it.
We have a cluster of 23 HP DL380p Gen8 hosts running Kafka. Basic specs:
2x E5-2650
128 GB RAM
12 x 4 TB 7200 RPM SATA
Le 25/05/2016 à 14:20, Nicolas Kovacs a écrit :
>
> - Is there a way to achieve this new resolution system-wide, and also
> for WindowMaker?
>
> I tried to fiddle a bit with xorg.conf (X -configure, copy it over, edit
> it), but to no avail.
>
I'll answer that myself, since I just found the
Hi Frank,
For your question, What should I do if I want to setup IPMI on my centos host?
1. Make sure your host hardware has BMC provided, typically a server does, but
a PC or laptop won't,
2. If so, use command "modprobe ipmi_si" or ipmi_devintf to load the kernel
device driver for BMC
> Yes, you are missing someting. :-) XEN_LOCK_DIR is used for a number
> of different things; but *only* "I am alive" init script files should
> live in /var/lock/subsys. (Presumably that's why it's a separate
> directory to begin with.) So the "proper" fix is to have the
> xendomains script
We are pleased to announce the immediate availability of CentOS Linux
6.8 and install media for i386 and x86_64 Architectures. Release Notes
for 6.8 are available at:
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.8
We recommend everyone review these release notes.
CentOS Linux 6.8 is
We have a new install of CentOS 6.7 with infiniband support installed.
We can see the card in hardware and we can see the mlx4 drivers loaded
in the kernel but cannot see the card as an ethernet interface, using
ifconfig -a. Can you recommend an install procedure to see this as an
ethernet
Yo tuve un problema de estos, y era incompatibilidad de la placa base
(no era un servidor, era un PC usado como servidor)
La placa en cuestión (y está documentado por ahí que por eso lo saqué
después de poner mas ventiladores, actualizar BIOS, cambiar memorias,
cambiar fuente, etc...) era una
Recomendacion: si vas a poner un server que es de "Alta Disponibilidad",
compralo nuevo !
Saludos !
El 25 de mayo de 2016, 8:44, Jorge Lluberas escribió:
> Estimados estoy teniendo problemas con un servidor que uso como proxy, cada
> tanto aparece apagado, no se si es un
es un clon que uso pero mas alla de eso, que es valido, quiero saber si
tengo forma de monitorear saber la causa en algun log, asumo que si la
temperatura por ejemplo es alta, deberia dejarlo registrado no ?
El 25 de mayo de 2016, 11:19, angel jauregui
escribió:
>
On Wed, May 25, 2016 at 07:34:05PM +0800, Frank Yu wrote:
>
> Hi all,
>
> I am trying to load kernel module ipmi_si, while failed with error "No such
> device", truth is I can find file in
> ../kernel/drivers/char/ipmi/ipmi_si.ko. So why I can't load it?
> [...]
> # modprobe ipmi_si
> FATAL:
Estimados estoy teniendo problemas con un servidor que uso como proxy, cada
tanto aparece apagado, no se si es un tema de la fuente, o calentamiento,
hay algun log donde pueda revisar o deje sentado la temperatura al momento
de apagarse, o la causa del porque se apaga ? esta instalado Centos 6
Gracias a todos me hacia falta activar esta linea NameVirtualHost
*:80,ahora esta funcionando ya los virtualhost, tengo un error en uno de
ellos pero me parece que es ya por un error de permisos gracias a todos
--
Saludos Cordiales
|César Martínez M. | Ingeniero de Sistemas | SERVICOM
|Tel:
Hi,
I'd like to run CentOS 7 in a KVM guest (host is my Slackware64 14.1
workstation). The main purpose of this installation will be to build
custom RPM packages. I've made a few tests, and everything works more or
less as expected. I'd like to resolve a small problem that's nagging me
though.
On 25/05/16 21:31, Anthony K wrote:
On 24/05/16 00:51, m.r...@5-cent.us wrote:
Is it possible to do what we want, and if so, some pointers would be
most appreciated.
mark
I believe *[0]* is what you are after. In summary:
lxc-cgroups -n cpuset.cpus 0-3
I've experimented
Hi all,
I am trying to load kernel module ipmi_si, while failed with error "No such
device", truth is I can find file in
../kernel/drivers/char/ipmi/ipmi_si.ko. So why I can't load it?
Steps:
# ls -l
/lib/modules/2.6.32-573.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko
-rwxr--r--. 1 root
On 25/05/16 03:08, Pat Haley wrote:
>
> Hi All,
>
> We looking for suggestions on dealing with mellanox drivers in CentOS 6.7
>
> We tried installing mellanox drivers
> (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64) on a Quanta Cirrascale
> server running Centos 6.7 -
On 24/05/16 00:51, m.r...@5-cent.us wrote:
Is it possible to do what we want, and if so, some pointers would be
most appreciated.
mark
I believe *[0]* is what you are after. In summary:
lxc-cgroups -n cpuset.cpus 0-3
I've experimented with it - *[1]*:
Regards,
ak.
On Tue, 24 May 2016 21:08:27 -0400
Pat Haley wrote:
> Hi All,
>
> We looking for suggestions on dealing with mellanox drivers in CentOS
> 6.7
Unless you really need a specific feature in MOFED I'd recommend you
stay with the, so called, in-box drivers already in CentOS-6.7.
We
On Tue, May 24, 2016 at 10:20 PM, exvito here wrote:
> On Tue, May 24, 2016 at 3:23 PM, George Dunlap wrote:
>>
>> The patches have been backported and are available in 4.6.1-9 from
>> virt-xen-testing. Please test it and report any problems here.
>>
>
Hi all,
I use centos7 and don't want to use tmpwatch as well as crond.
I have a question to use `systemd-tmpfiles-clean.service` with my custom
configured file in `tmpfiles.d` to delete outdated files periodically in
some log dir.
I have a `tmpfiles.d` configured file in `/etc/tmpfiles.d`
45 matches
Mail list logo