date:20170917

Re: [CentOS] audio flaky

2017-09-17 Thread Michael Hennebry


On Sat, 16 Sep 2017, mad.scientist.at.la...@tutanota.com wrote:


have you by chance, even accidentally turned on the volume normalization in 
vlc?  it doesn't work, and makes things get louder and softer in annoying ways.


The Normalize volume to: button is not checked
and the 2.00 is grayed out.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 7.4.1708 dependency problems

2017-09-17 Thread Gregory P. Ennis



Greg, according to the release notes "Known Issues" section ( 
https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7?action=show=Manuals%2FReleaseNotes%2FCentOS7.1708#head-281c090cc4fbc6bb5c7d4cd82a266fce807eee7c
 ) you need to run "yum downgrade libgpod" first.  I have updated a dozen or so 
machines to 7.4.1708, and several needed this.

-

Lamar,

Thanks much !!

Worked like a charm!

Greg

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] keepalived segfault after upgrade to 7.4

2017-09-17 Thread Phil Manuel

Prior to upgrading to CentOS 7.4 everything was fine, after upgrade I'm
seeing

/etc/keepalived# keepalived -f /etc/keepalived/keepalived.conf --dont-fork
--log-console --log-detail --dump-conf -m -v

Starting VRRP child process, pid=17224
Registering Kernel netlink reflector
Registering Kernel netlink command channel
Registering gratuitous ARP shared channel
Opening file '/etc/keepalived/keepalived.conf'.
VRRP_Instance(VI_1) removing protocol VIPs.
Keepalived_vrrp exited due to segmentation fault (SIGSEGV).
Please report a bug at https://github.com/acassen/keepalived/issues
and include this log from when keepalived started, what happened
immediately before the crash, and your configuration file.

KLeepalived just respawns, segfaults, respawns ...

Someone else has reported a similar issue,
https://github.com/acassen/keepalived/issues/650

Regards


Phil
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] Arranque servicios en Centos 6.9

2017-09-17 Thread domingov

Prueba vía consola serio o ntsysv... Lo mismo para ambiente X

Saludos

Sent from MailDroid

-Original Message-
From: "Gonzalo Faramiñan" 
To: centos-es@centos.org
Sent: dom., 17 sept. 2017 13:14
Subject: Re: [CentOS-es] Arranque servicios en Centos 6.9

No sé si habrás probado lo siguiente:

chkconfig --list

Eso te dirá el runlevel para el cual está configurado cada servicio. Si
estás en un servidor deberías habilitar el servicio en nivel 3, si es con
interfaz gráfica en nivel 5

https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-services-chkconfig.html

Por otro lado, para tener en cuenta, CentOS 7 utiliza systemd para
administrar los servicios, por lo que ya no utilizas chkconfig.



El 16 de septiembre de 2017, 07:52, L.C. - Salman PSL<
listascor...@salman.net> escribió:

>
> :: Me vais a perdonar, pero me estoy volviendo gili bueno loco.
>
> Resulta que ha vuelto a hacer una instalacion desde cero en un disco nuevo
> de 1 TB.
>
> Aparentemente la instalacion fue bien.
>
> Pero cuando quiero configurar los servicios a levantar en el arranque, no
> me funciona.
>
> Yo lo del arrancar y parar en Centos 5 siempre lo hacia mediante Webmin, y
> no me preocupaba de lo que hacia.
>
> Ahora con Centos 6 el Webmin me muestra un listado distinto y no me hace
> caso a la configuracion que le  doy.
>
> Y si lo hago manualmente tampoco me hace nada, tengo que entrar por
> teclado y levantar los servicios uno a uno  /iptables start
>
> Por mas que le he preguntado al Sr. Google, siempre me encuentro lo mismo
>
> chkconfig servicio on
>
> Pero cada vez que reinicio no inicia casi nada:
>
>  PID TTY  STAT   TIME COMMAND
> 2 ?S  0:00 [kthreadd]
> 3 ?S  0:00  \_ [migration/0]
> 4 ?S  0:00  \_ [ksoftirqd/0]
> 5 ?S  0:00  \_ [stopper/0]
> 6 ?S  0:00  \_ [watchdog/0]
> 7 ?S  0:00  \_ [migration/1]
> 8 ?S  0:00  \_ [stopper/1]
> 9 ?S  0:00  \_ [ksoftirqd/1]
>10 ?S  0:00  \_ [watchdog/1]
>11 ?S  0:00  \_ [migration/2]
>12 ?S  0:00  \_ [stopper/2]
>13 ?S  0:00  \_ [ksoftirqd/2]
>14 ?S  0:00  \_ [watchdog/2]
>15 ?S  0:00  \_ [migration/3]
>16 ?S  0:00  \_ [stopper/3]
>17 ?S  0:00  \_ [ksoftirqd/3]
>18 ?S  0:00  \_ [watchdog/3]
>19 ?S  0:00  \_ [events/0]
>20 ?S  0:00  \_ [events/1]
>21 ?S  0:00  \_ [events/2]
>22 ?S  0:00  \_ [events/3]
>23 ?S  0:00  \_ [events/0]
>24 ?S  0:00  \_ [events/1]
>25 ?S  0:00  \_ [events/2]
>26 ?S  0:00  \_ [events/3]
>27 ?S  0:00  \_ [events_long/0]
>28 ?S  0:00  \_ [events_long/1]
>29 ?S  0:00  \_ [events_long/2]
>30 ?S  0:00  \_ [events_long/3]
>31 ?S  0:00  \_ [events_power_ef]
>32 ?S  0:00  \_ [events_power_ef]
>33 ?S  0:00  \_ [events_power_ef]
>34 ?S  0:00  \_ [events_power_ef]
>35 ?S  0:00  \_ [cgroup]
>36 ?S  0:00  \_ [khelper]
>37 ?S  0:00  \_ [netns]
>38 ?S  0:00  \_ [async/mgr]
>39 ?S  0:00  \_ [pm]
>40 ?S  0:00  \_ [sync_supers]
>41 ?S  0:00  \_ [bdi-default]
>42 ?S  0:00  \_ [kintegrityd/0]
>43 ?S  0:00  \_ [kintegrityd/1]
>44 ?S  0:00  \_ [kintegrityd/2]
>45 ?S  0:00  \_ [kintegrityd/3]
>46 ?S  0:00  \_ [kblockd/0]
>47 ?S  0:00  \_ [kblockd/1]
>48 ?S  0:00  \_ [kblockd/2]
>49 ?S  0:00  \_ [kblockd/3]
>50 ?S  0:00  \_ [kacpid]
>51 ?S  0:00  \_ [kacpi_notify]
>52 ?S  0:00  \_ [kacpi_hotplug]
>53 ?S  0:00  \_ [ata_aux]
>54 ?S  0:00  \_ [ata_sff/0]
>55 ?S  0:00  \_ [ata_sff/1]
>56 ?S  0:00  \_ [ata_sff/2]
>57 ?S  0:00  \_ [ata_sff/3]
>58 ?S  0:00  \_ [ksuspend_usbd]
>59 ?S  0:00  \_ [khubd]
>60 ?S  0:00  \_ [kseriod]
>61 ?S  0:00  \_ [md/0]
>62 ?S  0:00  \_ [md/1]
>63 ?S  0:00  \_ [md/2]
>64 ?S  0:00  \_ [md/3]
>65 ?S  0:00  \_ [md_misc/0]
>66 ?S  0:00  \_ [md_misc/1]
>67 ?S  0:00  \_ [md_misc/2]
>68 ?S  0:00  \_ [md_misc/3]
>69 ?S  0:00  \_ [linkwatch]
>99 ?S  0:00  \_ [khungtaskd]
>   100 ?S  0:00  \_ [kswapd0]
>   101 ?SN 0:00  \_ [ksmd]
>   102 ?SN 0:00  \_ [khugepaged]
>   103 ?S  0:00  \_ [aio/0]
>

Re: [CentOS-es] Arranque servicios en Centos 6.9

2017-09-17 Thread Gonzalo Faramiñan

No sé si habrás probado lo siguiente:

chkconfig --list

Eso te dirá el runlevel para el cual está configurado cada servicio. Si
estás en un servidor deberías habilitar el servicio en nivel 3, si es con
interfaz gráfica en nivel 5

https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-services-chkconfig.html

Por otro lado, para tener en cuenta, CentOS 7 utiliza systemd para
administrar los servicios, por lo que ya no utilizas chkconfig.



El 16 de septiembre de 2017, 07:52, L.C. - Salman PSL<
listascor...@salman.net> escribió:

>
> :: Me vais a perdonar, pero me estoy volviendo gili bueno loco.
>
> Resulta que ha vuelto a hacer una instalacion desde cero en un disco nuevo
> de 1 TB.
>
> Aparentemente la instalacion fue bien.
>
> Pero cuando quiero configurar los servicios a levantar en el arranque, no
> me funciona.
>
> Yo lo del arrancar y parar en Centos 5 siempre lo hacia mediante Webmin, y
> no me preocupaba de lo que hacia.
>
> Ahora con Centos 6 el Webmin me muestra un listado distinto y no me hace
> caso a la configuracion que le  doy.
>
> Y si lo hago manualmente tampoco me hace nada, tengo que entrar por
> teclado y levantar los servicios uno a uno  /iptables start
>
> Por mas que le he preguntado al Sr. Google, siempre me encuentro lo mismo
>
> chkconfig servicio on
>
> Pero cada vez que reinicio no inicia casi nada:
>
>  PID TTY  STAT   TIME COMMAND
> 2 ?S  0:00 [kthreadd]
> 3 ?S  0:00  \_ [migration/0]
> 4 ?S  0:00  \_ [ksoftirqd/0]
> 5 ?S  0:00  \_ [stopper/0]
> 6 ?S  0:00  \_ [watchdog/0]
> 7 ?S  0:00  \_ [migration/1]
> 8 ?S  0:00  \_ [stopper/1]
> 9 ?S  0:00  \_ [ksoftirqd/1]
>10 ?S  0:00  \_ [watchdog/1]
>11 ?S  0:00  \_ [migration/2]
>12 ?S  0:00  \_ [stopper/2]
>13 ?S  0:00  \_ [ksoftirqd/2]
>14 ?S  0:00  \_ [watchdog/2]
>15 ?S  0:00  \_ [migration/3]
>16 ?S  0:00  \_ [stopper/3]
>17 ?S  0:00  \_ [ksoftirqd/3]
>18 ?S  0:00  \_ [watchdog/3]
>19 ?S  0:00  \_ [events/0]
>20 ?S  0:00  \_ [events/1]
>21 ?S  0:00  \_ [events/2]
>22 ?S  0:00  \_ [events/3]
>23 ?S  0:00  \_ [events/0]
>24 ?S  0:00  \_ [events/1]
>25 ?S  0:00  \_ [events/2]
>26 ?S  0:00  \_ [events/3]
>27 ?S  0:00  \_ [events_long/0]
>28 ?S  0:00  \_ [events_long/1]
>29 ?S  0:00  \_ [events_long/2]
>30 ?S  0:00  \_ [events_long/3]
>31 ?S  0:00  \_ [events_power_ef]
>32 ?S  0:00  \_ [events_power_ef]
>33 ?S  0:00  \_ [events_power_ef]
>34 ?S  0:00  \_ [events_power_ef]
>35 ?S  0:00  \_ [cgroup]
>36 ?S  0:00  \_ [khelper]
>37 ?S  0:00  \_ [netns]
>38 ?S  0:00  \_ [async/mgr]
>39 ?S  0:00  \_ [pm]
>40 ?S  0:00  \_ [sync_supers]
>41 ?S  0:00  \_ [bdi-default]
>42 ?S  0:00  \_ [kintegrityd/0]
>43 ?S  0:00  \_ [kintegrityd/1]
>44 ?S  0:00  \_ [kintegrityd/2]
>45 ?S  0:00  \_ [kintegrityd/3]
>46 ?S  0:00  \_ [kblockd/0]
>47 ?S  0:00  \_ [kblockd/1]
>48 ?S  0:00  \_ [kblockd/2]
>49 ?S  0:00  \_ [kblockd/3]
>50 ?S  0:00  \_ [kacpid]
>51 ?S  0:00  \_ [kacpi_notify]
>52 ?S  0:00  \_ [kacpi_hotplug]
>53 ?S  0:00  \_ [ata_aux]
>54 ?S  0:00  \_ [ata_sff/0]
>55 ?S  0:00  \_ [ata_sff/1]
>56 ?S  0:00  \_ [ata_sff/2]
>57 ?S  0:00  \_ [ata_sff/3]
>58 ?S  0:00  \_ [ksuspend_usbd]
>59 ?S  0:00  \_ [khubd]
>60 ?S  0:00  \_ [kseriod]
>61 ?S  0:00  \_ [md/0]
>62 ?S  0:00  \_ [md/1]
>63 ?S  0:00  \_ [md/2]
>64 ?S  0:00  \_ [md/3]
>65 ?S  0:00  \_ [md_misc/0]
>66 ?S  0:00  \_ [md_misc/1]
>67 ?S  0:00  \_ [md_misc/2]
>68 ?S  0:00  \_ [md_misc/3]
>69 ?S  0:00  \_ [linkwatch]
>99 ?S  0:00  \_ [khungtaskd]
>   100 ?S  0:00  \_ [kswapd0]
>   101 ?SN 0:00  \_ [ksmd]
>   102 ?SN 0:00  \_ [khugepaged]
>   103 ?S  0:00  \_ [aio/0]
>   104 ?S  0:00  \_ [aio/1]
>   105 ?S  0:00  \_ [aio/2]
>   106 ?S  0:00  \_ [aio/3]
>   107 ?S  0:00  \_ [crypto/0]
>   108 ?S  0:00  \_ [crypto/1]
>   109 ?S  0:00  \_ [crypto/2]
>   110 ?S  0:00  \_

Re: [CentOS] workaround using CentOS Plus Kernel? -- for 7.4 does not support PV [Xen]

2017-09-17 Thread Akemi Yagi

On Sun, Sep 17, 2017 at 7:54 AM,  wrote:

> Relates to: https://prgmr.com/blog/2017/09/14/centos-7-pv-unsupported.html
>
> I'm considering switching to the **CentOS Plus Kernel**.  What are the
> downsides?
> In the link above,  will the CentOS Plus Kernel get upgraded or will it be
> locked
> at a specific kernel?
>

The CentOSPlus kernel is updated whenever the distro kernel gets updated.

Akemi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] workaround using CentOS Plus Kernel? -- for 7.4 does not support PV [Xen]

2017-09-17 Thread centos

Relates to: https://prgmr.com/blog/2017/09/14/centos-7-pv-unsupported.html

I'm considering switching to the **CentOS Plus Kernel**.  What are the 
downsides?
In the link above,  will the CentOS Plus Kernel get upgraded or will it be 
locked
at a specific kernel?

--
thanks!,
Tom
--
https://wiki.centos.org/AdditionalResources/Repositories/CentOSPlus
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] (no subject)

2017-09-17 Thread centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] sysconf and _SC_LEVEL1_DCACHE_LINESIZE returns 0?

2017-09-17 Thread Jeffrey Walton

Hi Everyone,

I'm working on GCC112, which is POWER System S822 (Power8) machine
running CentOS 7 machine (https://gcc.gnu.org/wiki/CompileFarm):

$ cat /etc/centos-release
CentOS Linux release 7.3.1611 (AltArch)

I'm trying to determine L1 data cache size. When the following code
runs it returns 0. The man pages state -1 is an error, so I think its
claiming to succeed.

cacheLineSize = sysconf(_SC_LEVEL1_DCACHE_LINESIZE);

GCC119, which is also a S822 Power8 running AIX, returns 128.

Does anyone know what I might be doing wrong under Cent? Or maybe, how
can I retrieve the L1 data cache line size?

Thanks in advance.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] audio flaky

Re: [CentOS] Centos 7.4.1708 dependency problems

[CentOS] keepalived segfault after upgrade to 7.4

Re: [CentOS-es] Arranque servicios en Centos 6.9

Re: [CentOS-es] Arranque servicios en Centos 6.9

Re: [CentOS] workaround using CentOS Plus Kernel? -- for 7.4 does not support PV [Xen]

[CentOS] workaround using CentOS Plus Kernel? -- for 7.4 does not support PV [Xen]

[CentOS] (no subject)

[CentOS] sysconf and _SC_LEVEL1_DCACHE_LINESIZE returns 0?

9 matches

Site Navigation

Mail list logo

Footer information