[CentOS-announce] CESA-2013:0742 Low CentOS 6 389-ds-base Update

2013-04-16 Thread Johnny Hughes

CentOS Errata and Security Advisory 2013:0742 Low

Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0742.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
cae404b070941e328fde9461d531e37406ef1267a953fb9cea268bfd803378cd  
389-ds-base-1.2.11.15-14.el6_4.i686.rpm
6b4d6f4edb3fb3cbad3e09937efed226088ee2f390f35b5e7f367a813460d051  
389-ds-base-devel-1.2.11.15-14.el6_4.i686.rpm
e2029fa2d0ae508da3d31625945be6d96943de7fa90071191354a4cc8a2086f2  
389-ds-base-libs-1.2.11.15-14.el6_4.i686.rpm

x86_64:
3a9b33d77a0502a2a321b99bfe0f426f878bedd77ecbbf3c5d40a2b8beb4279a  
389-ds-base-1.2.11.15-14.el6_4.x86_64.rpm
6b4d6f4edb3fb3cbad3e09937efed226088ee2f390f35b5e7f367a813460d051  
389-ds-base-devel-1.2.11.15-14.el6_4.i686.rpm
00419ac033d73e6982cf0b8cfcbf08eb8c7da9e009290c02401cdfa1b69ab370  
389-ds-base-devel-1.2.11.15-14.el6_4.x86_64.rpm
e2029fa2d0ae508da3d31625945be6d96943de7fa90071191354a4cc8a2086f2  
389-ds-base-libs-1.2.11.15-14.el6_4.i686.rpm
605a41f9fb4db0e64844f0e5fb262d20de068043e1af055361ca9f18866e8556  
389-ds-base-libs-1.2.11.15-14.el6_4.x86_64.rpm

Source:
05c6b18c66cf415f0d4f382ac5648cb54a9fa463b554d210acdc11ee07234dd5  
389-ds-base-1.2.11.15-14.el6_4.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce


[CentOS-announce] CESA-2013:0747 Moderate CentOS 5 kernel Update

2013-04-16 Thread Johnny Hughes

CentOS Errata and Security Advisory 2013:0747 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0747.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
481fdd65428249761fdfe83f5a64c586ec3439802887e0a8c3491a3e7a5206a3  
kernel-2.6.18-348.4.1.el5.i686.rpm
c6b58ded9a074854acf87af028607a31470c6f30b02ccba3bfbab56af7870d7e  
kernel-debug-2.6.18-348.4.1.el5.i686.rpm
dcdde36bc073f69f909cdb9eee635b6748bd7536dde8c5e1faad764d7e4b20e8  
kernel-debug-devel-2.6.18-348.4.1.el5.i686.rpm
32676b93a5f624c140bfe5fd9f4bcca2b37b770d5d439a7b8153ca9dcc75367a  
kernel-devel-2.6.18-348.4.1.el5.i686.rpm
0a12d7e6d7f0a23b306b5435b482cabed0510abc1db872d8e35a777d1472843c  
kernel-doc-2.6.18-348.4.1.el5.noarch.rpm
ff97cf60a4c08670ea693833cb92d98e744e0422fc37586cd1831d48823bb808  
kernel-headers-2.6.18-348.4.1.el5.i386.rpm
f49802f41aca7cdd10f6f8c7f2bca685b7c59aa899c5d4add23e2f4526ac22a0  
kernel-PAE-2.6.18-348.4.1.el5.i686.rpm
9de980911864a34e586a7ff4628e741d0828e6a269240315129304ad66dbd9a8  
kernel-PAE-devel-2.6.18-348.4.1.el5.i686.rpm
ca7d636afdf44de785ed7f422c787abfb7400606227a90e6176c68acdd09954d  
kernel-xen-2.6.18-348.4.1.el5.i686.rpm
62c3cfcd98d6d816ee225a770f1002f481cf00b17a05e0190bf7c6a70167a8c7  
kernel-xen-devel-2.6.18-348.4.1.el5.i686.rpm

x86_64:
d74cdb9d5b8df688b1256c5400da5dd063fcf49f5b133255ab5e57acc7a7abae  
kernel-2.6.18-348.4.1.el5.x86_64.rpm
84f6a832783c241e748e7ee2b38cca93e1126b09e954ad4852df1d272bfb1175  
kernel-debug-2.6.18-348.4.1.el5.x86_64.rpm
8a33e9da207104519cef818ac281040e86c235a58cf7615d548b108f67ffc81c  
kernel-debug-devel-2.6.18-348.4.1.el5.x86_64.rpm
553cb48b068ff63ae10ed4d57fb4b8cce9fae9cd7d781cdc6ea2bdde26d61845  
kernel-devel-2.6.18-348.4.1.el5.x86_64.rpm
0a12d7e6d7f0a23b306b5435b482cabed0510abc1db872d8e35a777d1472843c  
kernel-doc-2.6.18-348.4.1.el5.noarch.rpm
b0757a6461f40030d97c77c6daaa1e12e9ebc14b9736f401306e7af5e0504e95  
kernel-headers-2.6.18-348.4.1.el5.x86_64.rpm
243e467f089fe0d7613308f560055618c096051cdbe1ffd810423569258fc5de  
kernel-xen-2.6.18-348.4.1.el5.x86_64.rpm
19aeccb361e3cee050ffa2a9c2cce6a125a6babf70d637ea6fef714387097e9d  
kernel-xen-devel-2.6.18-348.4.1.el5.x86_64.rpm

Source:
ccd95a37b51da84a29e36910d61deda2f0392e75aa6f4aa59efb56ca2e966642  
kernel-2.6.18-348.4.1.el5.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce


[CentOS-announce] CESA-2013:0748 Moderate CentOS 6 krb5 Update

2013-04-16 Thread Johnny Hughes

CentOS Errata and Security Advisory 2013:0748 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0748.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
e1c73d9feac9096d137259bb65437f4bce1fea1488b5e73404904e9f77f37524  
krb5-devel-1.10.3-10.el6_4.2.i686.rpm
02833a88b11f68c5b7a8e79d37b6a5b364da700ba62799e8fc7a75e84128bcac  
krb5-libs-1.10.3-10.el6_4.2.i686.rpm
ca2861a5ced482173db0aa25f109ec2bef2a116131e03d903838cfba63ddc24c  
krb5-pkinit-openssl-1.10.3-10.el6_4.2.i686.rpm
1cc250291311de9a1c601f422c6c3be52e6a90c12e18959435921617eaa796be  
krb5-server-1.10.3-10.el6_4.2.i686.rpm
b2db31577d473fba2fdda0e82a9c15ab785d32802b4ca7530fc5e82307e030c7  
krb5-server-ldap-1.10.3-10.el6_4.2.i686.rpm
f35d9a2bd03c49e69901339fff46ab533860640cbd37802069e7079e9b8efde7  
krb5-workstation-1.10.3-10.el6_4.2.i686.rpm

x86_64:
e1c73d9feac9096d137259bb65437f4bce1fea1488b5e73404904e9f77f37524  
krb5-devel-1.10.3-10.el6_4.2.i686.rpm
adf8f5fda9db10ff7fbac1527d6c68297633e86879ee3fa4e25308e914a9de6a  
krb5-devel-1.10.3-10.el6_4.2.x86_64.rpm
02833a88b11f68c5b7a8e79d37b6a5b364da700ba62799e8fc7a75e84128bcac  
krb5-libs-1.10.3-10.el6_4.2.i686.rpm
981b4adf578e6ce0e12ec3d9de2d76167502fcdb0a8a0455ce716ae8344b14b4  
krb5-libs-1.10.3-10.el6_4.2.x86_64.rpm
3c0ba8475be830fa151d64a0dab397531079b356385aa042cad7d20ead764251  
krb5-pkinit-openssl-1.10.3-10.el6_4.2.x86_64.rpm
09fa580eb48f8b1d66b2c734a7499d625611b86ab40720c65f1254bff62a5bd3  
krb5-server-1.10.3-10.el6_4.2.x86_64.rpm
b2db31577d473fba2fdda0e82a9c15ab785d32802b4ca7530fc5e82307e030c7  
krb5-server-ldap-1.10.3-10.el6_4.2.i686.rpm
7bbbdb1933dc7c98bfcf1f5786aa2076a7d4efb42c4ec322764c8f951930e418  
krb5-server-ldap-1.10.3-10.el6_4.2.x86_64.rpm
7450da0e3532be1748d3d6744800aab6a92d6315ea9f7752fdc27ab0197f  
krb5-workstation-1.10.3-10.el6_4.2.x86_64.rpm

Source:
937e16e8fba47eeff1e2c535d4cbc29d51a9576d60dfe021fdf249deaceeb847  
krb5-1.10.3-10.el6_4.2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce


[CentOS-es] apoyo

2013-04-16 Thread VICTOR MANUEL VARGAS GONZALEZ


Buenos Días

Antes que nada quisiera dar las gracias por recibir este
email , ya que estoy empezando a usar centos 5 ,

Tengo el siguiente problema tengo instalado centos 5 y
MailScanner-4.84.5-3 pero cuando trato de instalarlo me marca lo siguiente (
./install.sh)

 

./install.sh:
line 107: rpmbuild: command not found

Your
/usr/src/redhat, /usr/src/RPM or /usr/src/packages

tree is
missing.

If you have
access to an RPM called rpm-build or rpmbuild

then
install it first and come back and try again.

 

Gracias por
su apoyo



  
___
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es


Re: [CentOS-es] apoyo

2013-04-16 Thread victor santana
Parece que te falta el creador de paquetes, prueba a instalarlo:

yum install rpm-build

salu2.


El 16 de abril de 2013 15:24, VICTOR MANUEL VARGAS GONZALEZ 
victor...@hotmail.com escribió:



 Buenos Días

 Antes que nada quisiera dar las gracias por recibir este
 email , ya que estoy empezando a usar centos 5 ,

 Tengo el siguiente problema tengo instalado centos 5 y
 MailScanner-4.84.5-3 pero cuando trato de instalarlo me marca lo siguiente
 (
 ./install.sh)



 ./install.sh:
 line 107: rpmbuild: command not found

 Your
 /usr/src/redhat, /usr/src/RPM or /usr/src/packages

 tree is
 missing.

 If you have
 access to an RPM called rpm-build or rpmbuild

 then
 install it first and come back and try again.



 Gracias por
 su apoyo




 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es

___
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es


Re: [CentOS-es] Cerrar Skype

2013-04-16 Thread César Martinez
Amigos he estado investigando con los links que me enviaron y la única 
forma que encontré como bloquear skype es aplicando estas reglas

iptables -I FORWARD -s 111.221.74.0/24 -j DROP
iptables -I FORWARD -s 111.221.77.0/24 -j DROP
iptables -I FORWARD -s 157.55.130.0/24 -j DROP
iptables -I FORWARD -s 157.55.235.0/24 -j DROP
iptables -I FORWARD -s 157.55.56.0/24 -j DROP
iptables -I FORWARD -s 157.56.52.0/24 -j DROP
iptables -I FORWARD -s 194.165.188.0/24 -j DROP
iptables -I FORWARD -s 195.46.253.0/24 -j DROP
iptables -I FORWARD -s 213.199.179.0/24 -j DROP
iptables -I FORWARD -s 63.245.217.0/24 -j DROP
iptables -I FORWARD -s 64.4.23.0/24 -j DROP
iptables -I FORWARD -s 65.55.223.0/24 -j DROP

Con esto se cierra todo el problema es que no deseo cerrar a todos sino 
solo a un grupo de ips, para ello cree un bucle pero no funciona igual 
se conectan todos al skype.

SKYPE_ALLOW=192.168.1.12 192.168.1.14 192.168.1.111
iptables -N SKYPE
iptables -I FORWARD -s 111.221.74.0/24 -j SKYPE
iptables -I FORWARD -s 111.221.77.0/24 -j SKYPE
iptables -I FORWARD -s 157.55.130.0/24 -j SKYPE
iptables -I FORWARD -s 157.55.235.0/24 -j SKYPE
iptables -I FORWARD -s 157.55.56.0/24 -j SKYPE
iptables -I FORWARD -s 157.56.52.0/24 -j SKYPE
iptables -I FORWARD -s 194.165.188.0/24 -j SKYPE
iptables -I FORWARD -s 195.46.253.0/24 -j SKYPE
iptables -I FORWARD -s 213.199.179.0/24 -j SKYPE
iptables -I FORWARD -s 63.245.217.0/24 -j SKYPE
iptables -I FORWARD -s 64.4.23.0/24 -j SKYPE
iptables -I FORWARD -s 65.55.223.0/24 -j SKYPE
## SKYPE ALLOW
for face in $SKYPE_ALLOW; do
 iptables -A SKYPE -s $face -j ACCEPT
done
iptables -A SKYPE -j REJECT


Gracias César






On 05/04/13 23:23, Diego Sanchez wrote:
 https://www.google.com.ar/webhp?sourceid=chrome-instantion=1ie=UTF-8#hl=es-419safe=offsclient=psy-abq=iptables%20skype%20blockingoq=gs_l=pbx=1fp=53cce59a2ffd2795ion=1bav=on.2,or.r_cp.r_qf.bvm=bv.44770516,d.eWUbiw=1280bih=669

 http://pingtool.org/block-skype-connection/

 El día 5 de abril de 2013 18:08, César Martinez
 cmarti...@servicomecuador.com escribió:
 Muchas gracias voy a probarlo y te comento como me fue

 César
 hola, yo no la uso de forma transparente sino configurando en cada pc,
 de todas formas te paso los parametros que añadí y me dices si funciona

 lo que hace esto es bloquearte todas las pantallas de formularios

 http_access allow !validUserAgent accesoskype
 http_access deny !validUserAgent

 en accesoskype pones a los que si pueden tener acceso.

 saludos



 Date: Fri, 5 Apr 2013 14:27:49 -0500
 From: cmarti...@servicomecuador.com
 To: centos-es@centos.org
 Subject: Re: [CentOS-es] Cerrar Skype

 Hola si uso squid de forma transparente

 César
 hola
 skype(el antiguo) habia sido un problema en la red que administramos, 
 pero logramos evitar que funcione,
 con un servidor proxy squid, si te vas el tema de patrones o direcciones 
 , por ahi no es. ¿usas squid?


 From: fernando.urru...@solex.cl
 Date: Fri, 5 Apr 2013 09:58:31 -0300
 To: centos-es@centos.org
 Subject: Re: [CentOS-es] Cerrar Skype

 Skipe:

 En una parte de su configuración(herramientas - opciones -
 avanzada - conexión), dice usar puertos 443 y 80 como alternativa de
 conexión, así a menos que tengas un firewall capa 7.
 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es
 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es

 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es
 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es

 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es



___
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es


Re: [CentOS-es] Cerrar Skype

2013-04-16 Thread César C .
hola creo que seria asi:
 
que tipo de politica tienes ? DROP ? ACCEPT?
luego
si esta en accept, primero permites luego deniegas.
si esta en drop entonces permites.

asi me funciona
 

 Date: Tue, 16 Apr 2013 15:41:02 -0500
 From: cmarti...@servicomecuador.com
 To: centos-es@centos.org
 Subject: Re: [CentOS-es] Cerrar Skype
 
 Amigos he estado investigando con los links que me enviaron y la única 
 forma que encontré como bloquear skype es aplicando estas reglas
 
 iptables -I FORWARD -s 111.221.74.0/24 -j DROP
 iptables -I FORWARD -s 111.221.77.0/24 -j DROP
 iptables -I FORWARD -s 157.55.130.0/24 -j DROP
 iptables -I FORWARD -s 157.55.235.0/24 -j DROP
 iptables -I FORWARD -s 157.55.56.0/24 -j DROP
 iptables -I FORWARD -s 157.56.52.0/24 -j DROP
 iptables -I FORWARD -s 194.165.188.0/24 -j DROP
 iptables -I FORWARD -s 195.46.253.0/24 -j DROP
 iptables -I FORWARD -s 213.199.179.0/24 -j DROP
 iptables -I FORWARD -s 63.245.217.0/24 -j DROP
 iptables -I FORWARD -s 64.4.23.0/24 -j DROP
 iptables -I FORWARD -s 65.55.223.0/24 -j DROP
 
 Con esto se cierra todo el problema es que no deseo cerrar a todos sino 
 solo a un grupo de ips, para ello cree un bucle pero no funciona igual 
 se conectan todos al skype.
 
 SKYPE_ALLOW=192.168.1.12 192.168.1.14 192.168.1.111
 iptables -N SKYPE
 iptables -I FORWARD -s 111.221.74.0/24 -j SKYPE
 iptables -I FORWARD -s 111.221.77.0/24 -j SKYPE
 iptables -I FORWARD -s 157.55.130.0/24 -j SKYPE
 iptables -I FORWARD -s 157.55.235.0/24 -j SKYPE
 iptables -I FORWARD -s 157.55.56.0/24 -j SKYPE
 iptables -I FORWARD -s 157.56.52.0/24 -j SKYPE
 iptables -I FORWARD -s 194.165.188.0/24 -j SKYPE
 iptables -I FORWARD -s 195.46.253.0/24 -j SKYPE
 iptables -I FORWARD -s 213.199.179.0/24 -j SKYPE
 iptables -I FORWARD -s 63.245.217.0/24 -j SKYPE
 iptables -I FORWARD -s 64.4.23.0/24 -j SKYPE
 iptables -I FORWARD -s 65.55.223.0/24 -j SKYPE
 ## SKYPE ALLOW
 for face in $SKYPE_ALLOW; do
 iptables -A SKYPE -s $face -j ACCEPT
 done
 iptables -A SKYPE -j REJECT
 
 
 Gracias César
 
 
 
 
 
 
 On 05/04/13 23:23, Diego Sanchez wrote:
  https://www.google.com.ar/webhp?sourceid=chrome-instantion=1ie=UTF-8#hl=es-419safe=offsclient=psy-abq=iptables%20skype%20blockingoq=gs_l=pbx=1fp=53cce59a2ffd2795ion=1bav=on.2,or.r_cp.r_qf.bvm=bv.44770516,d.eWUbiw=1280bih=669
 
  http://pingtool.org/block-skype-connection/
 
  El día 5 de abril de 2013 18:08, César Martinez
  cmarti...@servicomecuador.com escribió:
  Muchas gracias voy a probarlo y te comento como me fue
 
  César
  hola, yo no la uso de forma transparente sino configurando en cada pc,
  de todas formas te paso los parametros que añadí y me dices si funciona
 
  lo que hace esto es bloquearte todas las pantallas de formularios
 
  http_access allow !validUserAgent accesoskype
  http_access deny !validUserAgent
 
  en accesoskype pones a los que si pueden tener acceso.
 
  saludos
 
 
 
  Date: Fri, 5 Apr 2013 14:27:49 -0500
  From: cmarti...@servicomecuador.com
  To: centos-es@centos.org
  Subject: Re: [CentOS-es] Cerrar Skype
 
  Hola si uso squid de forma transparente
 
  César
  hola
  skype(el antiguo) habia sido un problema en la red que administramos, 
  pero logramos evitar que funcione,
  con un servidor proxy squid, si te vas el tema de patrones o 
  direcciones , por ahi no es. ¿usas squid?
 
 
  From: fernando.urru...@solex.cl
  Date: Fri, 5 Apr 2013 09:58:31 -0300
  To: centos-es@centos.org
  Subject: Re: [CentOS-es] Cerrar Skype
 
  Skipe:
 
  En una parte de su configuración(herramientas - opciones -
  avanzada - conexión), dice usar puertos 443 y 80 como alternativa de
  conexión, así a menos que tengas un firewall capa 7.
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
 
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
 
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
 
 
 
 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es
  
___
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es


Re: [CentOS-es] Cerrar Skype

2013-04-16 Thread César Martínez Mora
Perdona no te entiendo 
-- 

Saludos
Ing César Martínez Mora 
Enviado desde mi móvil. HTC

César C. arvega...@hotmail.com escribió:

hola creo que seria asi:
 
que tipo de politica tienes ? DROP ? ACCEPT?
luego
si esta en accept, primero permites luego deniegas.
si esta en drop entonces permites.

asi me funciona
 

 Date: Tue, 16 Apr 2013 15:41:02 -0500
 From: cmarti...@servicomecuador.com
 To: centos-es@centos.org
 Subject: Re: [CentOS-es] Cerrar Skype
 
 Amigos he estado investigando con los links que me enviaron y la
única 
 forma que encontré como bloquear skype es aplicando estas reglas
 
 iptables -I FORWARD -s 111.221.74.0/24 -j DROP
 iptables -I FORWARD -s 111.221.77.0/24 -j DROP
 iptables -I FORWARD -s 157.55.130.0/24 -j DROP
 iptables -I FORWARD -s 157.55.235.0/24 -j DROP
 iptables -I FORWARD -s 157.55.56.0/24 -j DROP
 iptables -I FORWARD -s 157.56.52.0/24 -j DROP
 iptables -I FORWARD -s 194.165.188.0/24 -j DROP
 iptables -I FORWARD -s 195.46.253.0/24 -j DROP
 iptables -I FORWARD -s 213.199.179.0/24 -j DROP
 iptables -I FORWARD -s 63.245.217.0/24 -j DROP
 iptables -I FORWARD -s 64.4.23.0/24 -j DROP
 iptables -I FORWARD -s 65.55.223.0/24 -j DROP
 
 Con esto se cierra todo el problema es que no deseo cerrar a todos
sino 
 solo a un grupo de ips, para ello cree un bucle pero no funciona
igual 
 se conectan todos al skype.
 
 SKYPE_ALLOW=192.168.1.12 192.168.1.14 192.168.1.111
 iptables -N SKYPE
 iptables -I FORWARD -s 111.221.74.0/24 -j SKYPE
 iptables -I FORWARD -s 111.221.77.0/24 -j SKYPE
 iptables -I FORWARD -s 157.55.130.0/24 -j SKYPE
 iptables -I FORWARD -s 157.55.235.0/24 -j SKYPE
 iptables -I FORWARD -s 157.55.56.0/24 -j SKYPE
 iptables -I FORWARD -s 157.56.52.0/24 -j SKYPE
 iptables -I FORWARD -s 194.165.188.0/24 -j SKYPE
 iptables -I FORWARD -s 195.46.253.0/24 -j SKYPE
 iptables -I FORWARD -s 213.199.179.0/24 -j SKYPE
 iptables -I FORWARD -s 63.245.217.0/24 -j SKYPE
 iptables -I FORWARD -s 64.4.23.0/24 -j SKYPE
 iptables -I FORWARD -s 65.55.223.0/24 -j SKYPE
 ## SKYPE ALLOW
 for face in $SKYPE_ALLOW; do
 iptables -A SKYPE -s $face -j ACCEPT
 done
 iptables -A SKYPE -j REJECT
 
 
 Gracias César
 
 
 
 
 
 
 On 05/04/13 23:23, Diego Sanchez wrote:
 
https://www.google.com.ar/webhp?sourceid=chrome-instantion=1ie=UTF-8#hl=es-419safe=offsclient=psy-abq=iptables%20skype%20blockingoq=gs_l=pbx=1fp=53cce59a2ffd2795ion=1bav=on.2,or.r_cp.r_qf.bvm=bv.44770516,d.eWUbiw=1280bih=669
 
  http://pingtool.org/block-skype-connection/
 
  El día 5 de abril de 2013 18:08, César Martinez
  cmarti...@servicomecuador.com escribió:
  Muchas gracias voy a probarlo y te comento como me fue
 
  César
  hola, yo no la uso de forma transparente sino configurando en
cada pc,
  de todas formas te paso los parametros que añadí y me dices si
funciona
 
  lo que hace esto es bloquearte todas las pantallas de formularios
 
  http_access allow !validUserAgent accesoskype
  http_access deny !validUserAgent
 
  en accesoskype pones a los que si pueden tener acceso.
 
  saludos
 
 
 
  Date: Fri, 5 Apr 2013 14:27:49 -0500
  From: cmarti...@servicomecuador.com
  To: centos-es@centos.org
  Subject: Re: [CentOS-es] Cerrar Skype
 
  Hola si uso squid de forma transparente
 
  César
  hola
  skype(el antiguo) habia sido un problema en la red que
administramos, pero logramos evitar que funcione,
  con un servidor proxy squid, si te vas el tema de patrones o
direcciones , por ahi no es. ¿usas squid?
 
 
  From: fernando.urru...@solex.cl
  Date: Fri, 5 Apr 2013 09:58:31 -0300
  To: centos-es@centos.org
  Subject: Re: [CentOS-es] Cerrar Skype
 
  Skipe:
 
  En una parte de su configuración(herramientas - opciones -
  avanzada - conexión), dice usar puertos 443 y 80 como
alternativa de
  conexión, así a menos que tengas un firewall capa 7.
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
 
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
 
  ___
  CentOS-es mailing list
  CentOS-es@centos.org
  http://lists.centos.org/mailman/listinfo/centos-es
 
 
 
 ___
 CentOS-es mailing list
 CentOS-es@centos.org
 http://lists.centos.org/mailman/listinfo/centos-es
 
___
CentOS-es mailing list
CentOS-es@centos.org
http://lists.centos.org/mailman/listinfo/centos-es
___
CentOS-es mailing list
CentOS-es@centos.org

Re: [CentOS] My linux keeps logging me off when I run Firefox (how to debug)?

2013-04-16 Thread Nicolas Thierry-Mieg
Robert wrote:
 On Tue, 16 Apr 2013 00:30:15 + (UTC)
 Rock rocksock...@gmail.com wrote:

 So, you suggest I install the Nvidia drivers directly from Nvidia
 and not the Nvidia drivers from the El Repo repository?

 Note: I'm not sure I know how to do that.

 I too would suggest that you install the Nvidia drivers from the Nvidia site.

I would definitely advise you *not* to do that.
As someone pointed out in this thread, the nvidia-provided driver can 
mess with some system libs. The elrepo-provided one does not, and if it 
did you'ld know about it as rpm would detect a conflict.
Having the driver in an rpm is a huge plus.
...
ah, I see in a later email you went the elrepo way, well done!

Note that there are now 4 branches of the nvidia driver (3 legacy + 
latest), each supporting different devices. To know which branch you 
need, simply install nvidia-detect from elrepo and run it.
http://elrepo.org/tiki/nvidia-detect
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] how to capture packets that was forwarded

2013-04-16 Thread Jaze Lee
hello,
the topology is like this:

 centos v0:eth1 -- centos v0: eth2
  fc00:2:3:4::1  fc00:2:3::4

i turned the packet forwarding

ping6 -i eth2 fc00:2:3:4::1
the output is

PING fc00:2:3:4::1(fc00:2:3:4::1) from fc00:2:3::5 eth2: 56 data bytes
From fc00:2:3::4 icmp_seq=1 Destination unreachable: Administratively
prohibited
From fc00:2:3::4 icmp_seq=2 Destination unreachable: Administratively
prohibited
From fc00:2:3::4 icmp_seq=3 Destination unreachable: Administratively
prohibited
From fc00:2:3::4 icmp_seq=4 Destination unreachable: Administratively
prohibited

why the box do not forwarding icmp packets to eth2?
and how to set forwarding rules on centos 6.3?
Thanks
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Need Neighbour Discovery rpm for IPV6

2013-04-16 Thread Norah Jones
Hi, 

I need neighbour discovery rpm for IPV6 on CentOS 6.2 any pointer. Actually I 
am able to find out RHEL 5/CentOS 5 but could not locate CentOS 6 compatible 
RPM. 


Thanks,
Norah Jones


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


Re: [CentOS] My linux keeps logging me off when I run Firefox (how to debug)?

2013-04-16 Thread James Pearson
Rock wrote:
 On Tue, 16 Apr 2013 00:21:33 +, Rock wrote:
 
 
 Is there a Desktop crash log somewhere?
 
 
 Given that the advice was that X was crashing due to Nvidia 
 driver mismatch problems after my yum update, I took a look
 at the ~/.xsession-errors log file before and after the crash.
 
 And, you seem to be correct: The xsession is crashing when
 using Firefox (but not Chrome):
 
 Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) 
 on display ':0'.
 nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
 polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily 
 unavailable) on X server :0.
 nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server 
 :0.
 rhythmbox: Fatal IO error 11 (Resource temporarily unavailable) on X server 
 :0.
 gpk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X 
 server :0.
 pan: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
 gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X 
 server :0.
 gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) 
 on X server :0.
 gnome-terminal: Fatal IO error 104 (Connection reset by peer) on X server 
 :0.0.
 [14555:14555:0415/175602:ERROR:chrome_browser_main_x11.cc(62)] X IO error 
 received (X server probably went away)

Those messages are a result of Xorg crashing - i.e. various X11 apps 
complaining that Xorg has gone away ...

Any Xorg crash details will be in /var/log/Xorg.?.log - however, if Xorg 
has restarted since the crash, then the error should be in 
/var/log/Xorg.?.log.old

The error may also be in one of the log files in /var/log/gdm/

James Pearson

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


Re: [CentOS] how to capture packets that was forwarded

2013-04-16 Thread Andy Smith
Hi Jaze


On 16 April 2013 09:52, Jaze Lee jaze...@gmail.com wrote:

 hello,
 the topology is like this:

  centos v0:eth1 -- centos v0: eth2
   fc00:2:3:4::1  fc00:2:3::4

 i turned the packet forwarding


If you are talking about forwarding on Centos V0, forwarding will have no
effect here.  You appear to be trying to ping eth1 from a box somewhere on
eth2's network.
This is still classed as an input to V0 and will be handled by the INPUT
chain.


 ping6 -i eth2 fc00:2:3:4::1
 the output is

 PING fc00:2:3:4::1(fc00:2:3:4::1) from fc00:2:3::5 eth2: 56 data bytes
 From fc00:2:3::4 icmp_seq=1 Destination unreachable: Administratively
 prohibited
 From fc00:2:3::4 icmp_seq=2 Destination unreachable: Administratively
 prohibited
 From fc00:2:3::4 icmp_seq=3 Destination unreachable: Administratively
 prohibited
 From fc00:2:3::4 icmp_seq=4 Destination unreachable: Administratively
 prohibited


Administratively prohibited looks like a firewall issue.
Check your IPv6 firewall settings on V0


 why the box do not forwarding icmp packets to eth2?
 and how to set forwarding rules on centos 6.3?
 Thanks
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

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


Re: [CentOS] Need Neighbour Discovery rpm for IPV6

2013-04-16 Thread Karanbir Singh
On 04/16/2013 09:35 AM, Norah Jones wrote:
 Hi, 
 
 I need neighbour discovery rpm for IPV6 on CentOS 6.2 any pointer. Actually I 
 am able to find out RHEL 5/CentOS 5 but could not locate CentOS 6 compatible 
 RPM. 


what rpm is that ? neighbour discovery is a feature of the underlaying
network stack and justworks in ipv6


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Regarding : ATI video driver problems

2013-04-16 Thread Ned Slider
On 16/04/13 01:01, Mark LaPierre wrote:
 I gather from the discussion on the reference thread that I'll be having
 quite a time with a MB having an Integrated ATI Radeon HD 3000 graphics
 chip set and a video card using a Radeon HD 6570 chip set when I try to
 run CentOS 6.4 on it.

 I was going to ask if CrossFire works with CentOS, but it appears that
 the integrated chip set isn't going to work at all.


I can't answer the rest of your queries, but I will clarify one small 
point above - the integrated ATI Radeon HD 3000 graphics chipset will 
work with CentOS, it just isn't supported by the ATI/AMD proprietary 
driver under 6.4 (which I guess is what you meant above). But to clarify 
it is supported by the stock kernel driver in CentOS 6.4.

Whether that will allow for CrossFire and/or other more advanced 
configurations I do not know, and hopefully someone else will be able to 
answer.

 Well, ignoring all that, is CrossFire supported by any of the drivers
 available for CentOS 6.4?  If no then what about SLI support?  I don't
 want to paint myself into a corner by building a computer that I'll
 never get working to full potential.

 Anyway, here's my wish list as it stands at the moment.

   Brand   Model_Num
 Mother Board  GIGABYTEGA-78LMT-USB3
 Processor AMD FX-8150
 CPU Cooler
 Case  Cooler Master   HAF 912 RC-912-KKN1
 Power Supply  Cooler Master   RS650-ACAAE3-US
 MemoryCORSAIR CMX32GX3M4A1333C9
 DVD BurnerLite-On IHAS324-98
 Hard DriveSeagate ST1000DM003
 Video CardGIGABYTEGV-R657OC-1GI

 Feel free to suggest changes that might make compatibility less of an
 issue.  I chose the MB because it supports 32G of RAM and also has a
 parallel port that I need to support my laser printer.  I suppose I
 could use a parallel port interface card with another MB instead.


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


[CentOS] CentOS-announce Digest, Vol 98, Issue 7

2013-04-16 Thread centos-announce-request
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of CentOS-announce digest...


Today's Topics:

   1. CESA-2013:0742 Low CentOS 6 389-ds-base Update (Johnny Hughes)


--

Message: 1
Date: Tue, 16 Apr 2013 11:10:18 +
From: Johnny Hughes joh...@centos.org
Subject: [CentOS-announce] CESA-2013:0742 Low CentOS 6 389-ds-base
Update
To: centos-annou...@centos.org
Message-ID: 20130416111018.ga17...@chakra.karan.org
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2013:0742 Low

Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0742.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
cae404b070941e328fde9461d531e37406ef1267a953fb9cea268bfd803378cd  
389-ds-base-1.2.11.15-14.el6_4.i686.rpm
6b4d6f4edb3fb3cbad3e09937efed226088ee2f390f35b5e7f367a813460d051  
389-ds-base-devel-1.2.11.15-14.el6_4.i686.rpm
e2029fa2d0ae508da3d31625945be6d96943de7fa90071191354a4cc8a2086f2  
389-ds-base-libs-1.2.11.15-14.el6_4.i686.rpm

x86_64:
3a9b33d77a0502a2a321b99bfe0f426f878bedd77ecbbf3c5d40a2b8beb4279a  
389-ds-base-1.2.11.15-14.el6_4.x86_64.rpm
6b4d6f4edb3fb3cbad3e09937efed226088ee2f390f35b5e7f367a813460d051  
389-ds-base-devel-1.2.11.15-14.el6_4.i686.rpm
00419ac033d73e6982cf0b8cfcbf08eb8c7da9e009290c02401cdfa1b69ab370  
389-ds-base-devel-1.2.11.15-14.el6_4.x86_64.rpm
e2029fa2d0ae508da3d31625945be6d96943de7fa90071191354a4cc8a2086f2  
389-ds-base-libs-1.2.11.15-14.el6_4.i686.rpm
605a41f9fb4db0e64844f0e5fb262d20de068043e1af055361ca9f18866e8556  
389-ds-base-libs-1.2.11.15-14.el6_4.x86_64.rpm

Source:
05c6b18c66cf415f0d4f382ac5648cb54a9fa463b554d210acdc11ee07234dd5  
389-ds-base-1.2.11.15-14.el6_4.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

___
CentOS-announce mailing list
centos-annou...@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce


End of CentOS-announce Digest, Vol 98, Issue 7
**
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] how to capture packets that was forwarded

2013-04-16 Thread Jaze Lee
2013/4/16 Andy Smith spoo...@gmail.com

 Hi Jaze


 On 16 April 2013 09:52, Jaze Lee jaze...@gmail.com wrote:

  hello,
  the topology is like this:
 
   centos v0:eth1 -- centos v0: eth2
fc00:2:3:4::1  fc00:2:3::4
 
  i turned the packet forwarding
 

 If you are talking about forwarding on Centos V0, forwarding will have no
 effect here.  You appear to be trying to ping eth1 from a box somewhere on
 eth2's network.
 This is still classed as an input to V0 and will be handled by the INPUT
 chain.

 
  ping6 -i eth2 fc00:2:3:4::1
  the output is
 
  PING fc00:2:3:4::1(fc00:2:3:4::1) from fc00:2:3::5 eth2: 56 data bytes
  From fc00:2:3::4 icmp_seq=1 Destination unreachable: Administratively
  prohibited
  From fc00:2:3::4 icmp_seq=2 Destination unreachable: Administratively
  prohibited
  From fc00:2:3::4 icmp_seq=3 Destination unreachable: Administratively
  prohibited
  From fc00:2:3::4 icmp_seq=4 Destination unreachable: Administratively
  prohibited
 

 Administratively prohibited looks like a firewall issue.
 Check your IPv6 firewall settings on V0

   Thanks, it is truely because firewall issue. It's ok when i turned
ip6tables stoped.
Thank you all the same


 
  why the box do not forwarding icmp packets to eth2?
  and how to set forwarding rules on centos 6.3?
  Thanks
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




-- 
谦谦君子
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Need Neighbour Discovery rpm for IPV6

2013-04-16 Thread Steve Clark
On 04/16/2013 05:09 AM, Karanbir Singh wrote:
 On 04/16/2013 09:35 AM, Norah Jones wrote:
 Hi,

 I need neighbour discovery rpm for IPV6 on CentOS 6.2 any pointer. Actually 
 I am able to find out RHEL 5/CentOS 5 but could not locate CentOS 6 
 compatible RPM.

 what rpm is that ? neighbour discovery is a feature of the underlaying
 network stack and justworks in ipv6


It is important to understand that neighbor discovery depends on certain IPV6 
ping packets not being blocked to
work correctly.


 From RFC 4890
4.4.1.  Traffic That Must Not Be Dropped

Error messages that are essential to the establishment and
maintenance of communications:

o  Destination Unreachable (Type 1) - All codes
o  Packet Too Big (Type 2)
o  Time Exceeded (Type 3) - Code 0 only
o  Parameter Problem (Type 4) - Codes 1 and 2 only

Connectivity checking messages:

o  Echo Request (Type 128)
o  Echo Response (Type 129)

As discussed in Section 4.3.1, dropping connectivity checking
messages will prevent the firewall being the destination of a Teredo
tunnel and it is not considered necessary to disable connectivity
checking in IPv6 networks because port scanning is less of a security
risk.

There are a number of other sets of messages that play a role in
configuring the node and maintaining unicast and multicast
communications through the interfaces of a node.  These messages must
not be dropped if the node is to successfully participate in an IPv6
network.  The exception to this is the Redirect message for which an
explicit policy decision should be taken (see Section 4.4.4).

Address Configuration and Router Selection messages:

o  Router Solicitation (Type 133)
o  Router Advertisement (Type 134)
o  Neighbor Solicitation (Type 135)
o  Neighbor Advertisement (Type 136)
o  Inverse Neighbor Discovery Solicitation (Type 141)
o  Inverse Neighbor Discovery Advertisement (Type 142)


-- 
Stephen Clark
*NetWolves*
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] New motherboard - kernel panic

2013-04-16 Thread Bowie Bailey
On 4/15/2013 5:09 PM, m.r...@5-cent.us wrote:
 Bowie Bailey wrote:
 On 4/15/2013 1:35 PM, m.r...@5-cent.us wrote:
 Bowie Bailey wrote:
 On 4/12/2013 5:33 PM, Bowie Bailey wrote:
 I had to replace the motherboard on one of my CentOS 4 systems and am
 now getting a kernel panic.

 When I try to boot up, I get this:

   Volume group VolGroup00 not found
 ERROR: /bin/lvm exited abnormally! (pid 448)
 mount: error 6 mounting ext3
 mount: error 2 mounting none
 switchroot: mount failed: 22
 umount /initrd/dev failed: 2
 Kernel panic - not syncing: Attempted to kill init!

 (I apologize for any typos, I don't have a way to copy/paste from that
 screen)

 I can boot up with the boot CD, go into rescue mode and browse the
 files, so I know the drives are ok.

 I found some stuff online saying that I should recreate my initrd from
 rescue mode if the motherboard changed.  I tried this, but am still
 getting the same results.
 Sorry, hit send and had another thought: I think you said you rebuilt
 the initrd... *could* you see the drives? *Did* the running system you
 rebuilt from have all the LVM drivers loaded when you rebuilt it?
 I can see the drives from the rescue environment.  I don't know how to
 check the LVM drivers.
 You need *both* the md drivers and lvm drivers. I haven't built a system
 using lvm in years, I'm afraid, but it shouldn't be too hard.

 Btw, this may be of some interest:
 http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/device_mapper.html

I got it figured out.  The problem was at the sata driver level. The 
instructions I found for rebuilding the initrd neglected to mention that 
I needed to edit modprobe.conf and add the appropriate driver 
information first.

I'm still not sure why it was able to get as far as loading the kernel 
before suddenly being unable to see the drives.  If it needs sata 
drivers to see the disks, why doesn't it need them to read the boot 
partition?  I didn't have to mess with grub or the boot sector after 
changing motherboards.

-- 
Bowie
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] My linux keeps logging me off when I run Firefox (how to debug)?

2013-04-16 Thread Rock
On Tue, 16 Apr 2013 09:55:27 +0100, James Pearson wrote:

 Any Xorg crash details will be in /var/log/Xorg.?.log - however, if Xorg 
 has restarted since the crash, then the error should be in 
 /var/log/Xorg.?.log.old
 
 The error may also be in one of the log files in /var/log/gdm/

Thanks James, 
This is helpful, especially for debugging.

I'm looking through the Xorg.?.log files in /var/log/
Xorg.{0,2,3,4,5,9}.log
Xorg.{0,,2,3,4,5}.log.old

There is a lot there - but I'm not sure what I'm looking for.

Likewise, I'm looking through the files in /var/log/gdm for clues:
:0-greeter.log
:0-greeter.log.{1,2,3,4}
:0.log
:0.log.{1,2,3,4}
:0-slave.log
:0-slave.log.{1,2,3,4}
etc.


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


Re: [CentOS] My linux keeps logging me off when I run Firefox (how to debug)?

2013-04-16 Thread Rock
On Tue, 16 Apr 2013 09:19:23 +0200, Nicolas Thierry-Mieg wrote:

 Note that there are now 4 branches of the nvidia driver (3 legacy + 
 latest), each supporting different devices. To know which branch you 
 need, simply install nvidia-detect from elrepo and run it.
 http://elrepo.org/tiki/nvidia-detect

Thanks!

The results from that program are nice because it is problematic
to obtain the correct driver version from the Nvidia support page
(due to multiple Quadro FX entries, only one of which is the correct
one - so one can easily conclude the wrong driver from the Nvidia
support pages).

I have, AFAIK, the Nvidia Quadro FX 880M graphics card:
$ /sbin/lspci -nn | grep VGA
  == 01:00.0 VGA compatible controller [0300]:
  NVIDIA Corporation GT216 [Quadro FX 880M] [10de:0a3c] (rev a2)

$ sudo yum --enablerepo elrepo install nvidia-detect
== Installed: nvidia-detect.x86_64 0:310.40-1.el6.elrepo 

$ nvidia-detect
Probing for supported NVIDIA devices...
[10de:0a3c] NVIDIA Corporation GT216 [Quadro FX 880M]
This device requires the current 310.40 NVIDIA driver (kmod-nvidia).


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


[CentOS] qmake package

2013-04-16 Thread Kaplan, Andrew H.
Hello --

I am running the release 6.2 32-bit distribution, and I am in need of the qmake 
utility in order to complete the installation
of an application. Can someone provide the name of the package, or packages, 
that would include the qmake software?

Thanks.



The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] qmake package

2013-04-16 Thread Bob Marcan
On Tue, 16 Apr 2013 15:21:30 +
Kaplan, Andrew H. ahkap...@partners.org wrote:

 Hello --
 
 I am running the release 6.2 32-bit distribution, and I am in need of the 
 qmake utility in order to complete the installation
 of an application. Can someone provide the name of the package, or packages, 
 that would include the qmake software?
 
 Thanks.

 yum provides \*/qmake

BR, Bob
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] New motherboard - kernel panic

2013-04-16 Thread Les Mikesell
On Tue, Apr 16, 2013 at 8:30 AM, Bowie Bailey bowie_bai...@buc.com wrote:

 I got it figured out.  The problem was at the sata driver level. The
 instructions I found for rebuilding the initrd neglected to mention that
 I needed to edit modprobe.conf and add the appropriate driver
 information first.

 I'm still not sure why it was able to get as far as loading the kernel
 before suddenly being unable to see the drives.  If it needs sata
 drivers to see the disks, why doesn't it need them to read the boot
 partition?  I didn't have to mess with grub or the boot sector after
 changing motherboards.

Grub uses the system bios to load the kernel and initrd.  Then the
kernel takes over and has to either have the needed
disk/raid/lvm/filesystem drivers compiled in or available as modules
in the initrd to be able continue and mount the drives.

--
  Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] My linux keeps logging me off when I run Firefox (how to debug)?

2013-04-16 Thread James Pearson
Rock wrote:
 On Tue, 16 Apr 2013 09:55:27 +0100, James Pearson wrote:
 
 Thanks James, 
 This is helpful, especially for debugging.
 
 I'm looking through the Xorg.?.log files in /var/log/
 Xorg.{0,2,3,4,5,9}.log
 Xorg.{0,,2,3,4,5}.log.old
 
 There is a lot there - but I'm not sure what I'm looking for.
 
 Likewise, I'm looking through the files in /var/log/gdm for clues:
 :0-greeter.log
 :0-greeter.log.{1,2,3,4}
 :0.log
 :0.log.{1,2,3,4}
 :0-slave.log
 :0-slave.log.{1,2,3,4}
 etc.

The numbers refer to the display X is running on - usually 0 - I would 
start of by looking at the end of /var/log/Xorg.0.log.old and/or 
/var/log/gdm/:0.log.1

James Pearson
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] 2nd NIC troubles

2013-04-16 Thread Jason T. Slack-Moehrle
Hi All,

I have 2 NICS in this system. CentOS 6.4

eth0 is the virtual IP from PFSense mapping connected to the router, works
fine.

eth1 is a second NIC that I have assigned a private IP to and connected it
to a switch on the private network. I have many other private devices, so I
know this setup works.

When I connect the cable to the switch and bring up eth1 the system
basically stops taking requests. I can no longer SSH in, Websites stop
responding, etc. If I walk over to the server and take down eth1,
everything works fine.

Here is eth0:
DEVICE=eth0
HWADDR=00:1b:21:cd:80:bf
TYPE=Ethernet
UUID=68a95912-3915-4b1a-9080-eb2017330153
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=none
IPADDR=192.168.1.27
NETMASK=255.255.255.0
DNS2=8.8.4.4
GATEWAY=192.168.1.1
DNS1=8.8.8.8
IPV6INIT=no
USERCTL=no

Here is eth1:
DEVICE=eth1
HWADDR=00:0a:cd:17:07:7e
TYPE=Ethernet
UUID=b3851363-ae9e-4066-8993-caed07b9945b
ONBOOT=no
NM_CONTROLLED=yes
BOOTPROTO=none
IPADDR=10.0.254.11
NETMASK=255.255.255.0
GATEWAY=10.0.254.1
DNS1=8.8.8.8
DNS2=8.8.4.4
IPV6INIT=no
USERCTL=no

I have never experienced this before.

Also, when I check system-config-network-tui, some .bak, which I made, but
deleted the files from the file system when I was trying a few things. But
how do I get rid of them?

I attached a screenshot

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


Re: [CentOS] 2nd NIC troubles

2013-04-16 Thread Michael Mol
On 04/16/2013 01:37 PM, Jason T. Slack-Moehrle wrote:
 Hi All,
 
 I have 2 NICS in this system. CentOS 6.4
 
 eth0 is the virtual IP from PFSense mapping connected to the router, works
 fine.
 
 eth1 is a second NIC that I have assigned a private IP to and connected it
 to a switch on the private network. I have many other private devices, so I
 know this setup works.
 
 When I connect the cable to the switch and bring up eth1 the system
 basically stops taking requests. I can no longer SSH in, Websites stop
 responding, etc. If I walk over to the server and take down eth1,
 everything works fine.
 
 Here is eth0:
 DEVICE=eth0
 HWADDR=00:1b:21:cd:80:bf
 TYPE=Ethernet
 UUID=68a95912-3915-4b1a-9080-eb2017330153
 ONBOOT=yes
 NM_CONTROLLED=yes
 BOOTPROTO=none
 IPADDR=192.168.1.27
 NETMASK=255.255.255.0
 DNS2=8.8.4.4
 GATEWAY=192.168.1.1
 DNS1=8.8.8.8
 IPV6INIT=no
 USERCTL=no
 
 Here is eth1:
 DEVICE=eth1
 HWADDR=00:0a:cd:17:07:7e
 TYPE=Ethernet
 UUID=b3851363-ae9e-4066-8993-caed07b9945b
 ONBOOT=no
 NM_CONTROLLED=yes
 BOOTPROTO=none
 IPADDR=10.0.254.11
 NETMASK=255.255.255.0
 GATEWAY=10.0.254.1
 DNS1=8.8.8.8
 DNS2=8.8.4.4
 IPV6INIT=no
 USERCTL=no
 
 I have never experienced this before.

Remove the GATEWAY line from eth1, unless you have another router (with
its own access to the Internet) at 10.0.254.1. If eth0 points at your
upstream, then this is unlikely.




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 2nd NIC troubles

2013-04-16 Thread Jason T. Slack-Moehrle
I do have another gateway at 10.0.254.1, it is a Linksys router that all
the provate stuff plugs into, and that Linksys plugs directly into our
modem.


On Tue, Apr 16, 2013 at 10:42 AM, Michael Mol mike...@gmail.com wrote:

 On 04/16/2013 01:37 PM, Jason T. Slack-Moehrle wrote:
  Hi All,
 
  I have 2 NICS in this system. CentOS 6.4
 
  eth0 is the virtual IP from PFSense mapping connected to the router,
 works
  fine.
 
  eth1 is a second NIC that I have assigned a private IP to and connected
 it
  to a switch on the private network. I have many other private devices,
 so I
  know this setup works.
 
  When I connect the cable to the switch and bring up eth1 the system
  basically stops taking requests. I can no longer SSH in, Websites stop
  responding, etc. If I walk over to the server and take down eth1,
  everything works fine.
 
  Here is eth0:
  DEVICE=eth0
  HWADDR=00:1b:21:cd:80:bf
  TYPE=Ethernet
  UUID=68a95912-3915-4b1a-9080-eb2017330153
  ONBOOT=yes
  NM_CONTROLLED=yes
  BOOTPROTO=none
  IPADDR=192.168.1.27
  NETMASK=255.255.255.0
  DNS2=8.8.4.4
  GATEWAY=192.168.1.1
  DNS1=8.8.8.8
  IPV6INIT=no
  USERCTL=no
 
  Here is eth1:
  DEVICE=eth1
  HWADDR=00:0a:cd:17:07:7e
  TYPE=Ethernet
  UUID=b3851363-ae9e-4066-8993-caed07b9945b
  ONBOOT=no
  NM_CONTROLLED=yes
  BOOTPROTO=none
  IPADDR=10.0.254.11
  NETMASK=255.255.255.0
  GATEWAY=10.0.254.1
  DNS1=8.8.8.8
  DNS2=8.8.4.4
  IPV6INIT=no
  USERCTL=no
 
  I have never experienced this before.

 Remove the GATEWAY line from eth1, unless you have another router (with
 its own access to the Internet) at 10.0.254.1. If eth0 points at your
 upstream, then this is unlikely.



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


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


Re: [CentOS] qmake package

2013-04-16 Thread Kaplan, Andrew H.
I found the answer. The qmake package was installed as qmake-qt4. 

The solution to the problem was to create a symbolic link called qmake
that pointed to the aforementioned binary.



-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Bob Marcan
Sent: Tuesday, April 16, 2013 11:35 AM
To: centos@centos.org
Subject: Re: [CentOS] qmake package

On Tue, 16 Apr 2013 15:21:30 +
Kaplan, Andrew H. ahkap...@partners.org wrote:

 Hello --
 
 I am running the release 6.2 32-bit distribution, and I am in need of the 
 qmake utility in order to complete the installation
 of an application. Can someone provide the name of the package, or packages, 
 that would include the qmake software?
 
 Thanks.

 yum provides \*/qmake

BR, Bob
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

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


Re: [CentOS] 2nd NIC troubles

2013-04-16 Thread John R Pierce
On 4/16/2013 11:05 AM, Jason T. Slack-Moehrle wrote:
 I do have another gateway at 10.0.254.1, it is a Linksys router that all
 the provate stuff plugs into, and that Linksys plugs directly into our
 modem.

multiple gateways is problematic.   there should be only one default 
route to 0.0.0.0/0


so you have a pfSense firewall AND a linksys soho router both connected 
to the internet? sounds messy.



-- 
john r pierce  37N 122W
somewhere on the middle of the left coast

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


Re: [CentOS] 2nd NIC troubles

2013-04-16 Thread Les Mikesell
On Tue, Apr 16, 2013 at 1:05 PM, Jason T. Slack-Moehrle
slackmoeh...@gmail.com wrote:
 I do have another gateway at 10.0.254.1, it is a Linksys router that all
 the provate stuff plugs into, and that Linksys plugs directly into our
 modem.

You can only have one 'default' gateway.  Keep the one pointed to the
internet router.  Make a file named
/etc/sysconfig/network-scripts/route-eth1 to hold the route(s) handled
by the other interface.  Something like:
10.0.0.0/8 via 10.0.254.1
should work if you want the whole private class A space to go that way.
The ifup/ifdown scripts will add/remove the routes matching the interfaces.

--
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] nfs4 and idmapd

2013-04-16 Thread Peter Wood
I'm using CentOS5.9 and mounting a remote directory via NFSv4. The nfs
server is OpenIndiana 151.a.7 (i.e. Solaris).

Users bin and daemon have each others ID on the oposite system.

On OpenIndiana:
  User: bin; ID=2
  User: daemon; ID=1

On CentOS:
  User: bin; ID=1
  User: daemon; ID=2

That means if I create a file as daemon on the client (CentOS), it gets
saved on the server as owner bin and it shows back on the client as owner
bin.

I'm trying to use idmapd to define custom mapping but I can't get it
working.

===
cat /etc/idmapd.conf
  [General]
  Verbosity = 5
  Domain = local

  [Mapping]
  Nobody-User = nobody
  Nobody-Group = nobody

  [Translation]
  Method = static,nsswitch

  [Static]
  bin@local = daemon

===
service rpcidmapd restart
In /var/log/messages:
  Apr 16 11:26:37 tzalt rpc.idmapd[29848]: libnfsidmap: using domain: local
  Apr 16 11:26:37 tzalt rpc.idmapd[29848]: libnfsidmap: processing 'Method'
list
  Apr 16 11:26:37 tzalt rpc.idmapd[29848]: libnfsidmap: loaded plugin
libnfsidmap_static.so for method static
  Apr 16 11:26:37 tzalt rpc.idmapd[29848]: libnfsidmap: loaded plugin
libnfsidmap_nsswitch.so for method nsswitch
  Apr 16 11:26:37 tzalt rpc.idmapd[29849]: Expiration time is 600 seconds.
  Apr 16 11:26:37 tzalt rpc.idmapd[29849]: nfsdopenone: Opening
/proc/net/rpc/nfs4.nametoid/channel failed: errno 2 (No such file or
directory)

I researched the error above and in a few places people say that it should
be ignored.

==
mount -t nfs4 srvstor15:/utils/depdata /utils/depdata
In /var/log/messages:
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: New client: 4b
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: Opened
/var/lib/nfs/rpc_pipefs//nfs/clnt4b/idmap
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: New client: 4c
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_uid: calling
nsswitch-name_to_uid
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nss_getpwnam: name 'root@local'
domain 'local': resulting localname 'root'
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_uid:
nsswitch-name_to_uid returned 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_uid: final return
value is 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: Client 4b: (user) name root@local
- id 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: calling
nsswitch-name_to_gid
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid:
nsswitch-name_to_gid returned -2
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: final return
value is -2
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: Client 4b: (group) name
staff@local - id 99
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: calling
nsswitch-name_to_gid
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid:
nsswitch-name_to_gid returned 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: final return
value is 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: Client 4b: (group) name root@local
- id 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_uid: calling
nsswitch-name_to_uid
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nss_getpwnam: name 'daemon@local'
domain 'local': resulting localname 'daemon'
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_uid:
nsswitch-name_to_uid returned 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_uid: final return
value is 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: Client 4b: (user) name
daemon@local - id 2
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: calling
nsswitch-name_to_gid
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid:
nsswitch-name_to_gid returned 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: final return
value is 0
Apr 16 11:28:42 tzalt rpc.idmapd[29849]: Client 4b: (group) name
daemon@local - id 2

==
sudo -u daemon touch /utils/depdata/bin/asdfDaemonF1
In /var/log/messages:
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: nfs4_name_to_uid: calling
nsswitch-name_to_uid
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: nss_getpwnam: name 'bin@local'
domain 'local': resulting localname 'bin'
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: nfs4_name_to_uid:
nsswitch-name_to_uid returned 0
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: nfs4_name_to_uid: final return
value is 0
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: Client 4b: (user) name bin@local
- id 1
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: calling
nsswitch-name_to_gid
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: nfs4_name_to_gid:
nsswitch-name_to_gid returned 0
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: nfs4_name_to_gid: final return
value is 0
Apr 16 11:31:56 tzalt rpc.idmapd[29849]: Client 4b: (group) name bin@local
- id 1

==
ls -l /utils/depdata/bin/asdfDaemonF1
-rw-r--r-- 1 bin bin 0 Apr 16 11:31 /utils/depdata/bin/asdfDaemonF1

The file is owned by user bin on the client and the server. But, I used
user daemon to create it.

Any suggestion how can I get this ownership in sync?

Thanks,

-- Peter
___
CentOS mailing list
CentOS@centos.org

Re: [CentOS] 2nd NIC troubles

2013-04-16 Thread Jason T. Slack-Moehrle
Hi John,

 I do have another gateway at 10.0.254.1, it is a Linksys router that all

  the provate stuff plugs into, and that Linksys plugs directly into our
  modem.

 multiple gateways is problematic.   there should be only one default
 route to 0.0.0.0/0


 so you have a pfSense firewall AND a linksys soho router both connected
 to the internet? sounds messy.


Yes, indeed. We have a pfsense box with servers behind it connected to our
modem as well as a router connected with private stuff behind it.

We do need to move the private stuff behind the pfsense box as well. It is
on the list.

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


Re: [CentOS] 2nd NIC troubles

2013-04-16 Thread Jason T. Slack-Moehrle
Hi Les,

  I do have another gateway at 10.0.254.1, it is a Linksys router that all
  the provate stuff plugs into, and that Linksys plugs directly into our
  modem.

 You can only have one 'default' gateway.  Keep the one pointed to the
 internet router.  Make a file named
 /etc/sysconfig/network-scripts/route-eth1 to hold the route(s) handled
 by the other interface.  Something like:
 10.0.0.0/8 via 10.0.254.1
 should work if you want the whole private class A space to go that way.
 The ifup/ifdown scripts will add/remove the routes matching the interfaces.


So this is a static route. I trued what you suggested and the eth1
interface stalls to come up. It just wont. All ssh sessions get
disconnected and everything stops working

I did:

[root@meowbox network-scripts]# cat route-eth1
10.0.0.0/8 via 10.0.254.1

I found:
http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-networkscripts-static-routes.html

So I changed it to:

[root@meowbox network-scripts]# cat route-eth1
10.0.0.0/8 via 10.0.254.1 dev eth1

and commented out the GATEWAY= line in ifcfg-eht1 and the interface comes
up.

Testing ssh and the websites, they seem to be fine.

Thank you for this lesson.

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


Re: [CentOS] 2nd NIC troubles

2013-04-16 Thread Les Mikesell
On Tue, Apr 16, 2013 at 2:26 PM, Jason T. Slack-Moehrle
slackmoeh...@gmail.com wrote:

 So this is a static route. I trued what you suggested and the eth1
 interface stalls to come up. It just wont. All ssh sessions get
 disconnected and everything stops working

 I did:

 [root@meowbox network-scripts]# cat route-eth1
 10.0.0.0/8 via 10.0.254.1

 I found:
 http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-networkscripts-static-routes.html

 So I changed it to:

 [root@meowbox network-scripts]# cat route-eth1
 10.0.0.0/8 via 10.0.254.1 dev eth1

Interesting - I've never had to specify the device when it can be
deduced from the interface IP and netmask.  And I've never been able
to make much sense out of the 'ip' man page either to tell what is
actually required.

--
  Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nfs4 and idmapd

2013-04-16 Thread Nicolas Thierry-Mieg
Peter Wood wrote:
 I'm using CentOS5.9 and mounting a remote directory via NFSv4. The nfs
 server is OpenIndiana 151.a.7 (i.e. Solaris).

 Users bin and daemon have each others ID on the oposite system.

 On OpenIndiana:
User: bin; ID=2
User: daemon; ID=1

 On CentOS:
User: bin; ID=1
User: daemon; ID=2

 That means if I create a file as daemon on the client (CentOS), it gets
 saved on the server as owner bin and it shows back on the client as owner
 bin.

 I'm trying to use idmapd to define custom mapping but I can't get it
 working.

don't know for idmapd, but if you have a simple setup you could switch 
the uids of bin and daemon on your client (and chown all their files of 
course).
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 4 monitors with one graphics card and standard driver

2013-04-16 Thread m . roth
Dale Dellutri wrote:
 I've just test an ATI FirePro 2460 graphics card on CentOS 6.4.  It
 connects 4 monitors.
 It worked with the standard radeon driver.  I was able to arrange the
 monitors into my preferred configuration (as a square array, 1 upper
 left, 2 lower left, 3 lower right, 4 upper right) simply by clicking
 System - Preferences - Display, and then moving the
 four monitor images.  This creates the file ~/.config/monitors.xml .
snip
 I also tested two other cards: ATI FirePro 2450 and NVidia Quadro NVS 420.
 For each of these cards, the BIOS shows the card in slot 1 as a PCI
 Bridge.
 lspci reports two identical video cards at 03:00.0 and 04:00.0.
 Though it's easy to set up two screens properly, xinerama would probably
 be required in an xorg.conf to get all four screens working properly.

Would you mind sending me your xorg.conf offlist? I *may* have found
something in the one I've been handcrafting, but as my user is busy, I
won't be able to try it out for a while, and would love to see what you
did.

I'm still at the point of him having one monitor working fine, but the
other comes up, not mirrored, but unreachable by keyboard or mouse.
Looking at his old xorg.conf that worked with kmod-fglrx, and my own (an
NVidia card) I realized they only have one Screen sectiuon, and a viewport
on his (mine, of course, has twinview), so I've just edited his that way.

mark

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


[CentOS] inittab - huh what's it good for?

2013-04-16 Thread James B. Byrne
We run a CentOS-5 based hylafax server with external serial modems. We
are transitioning to an Asterisk system using IAXmodem running on
CentOS-6.

On the CentOS-5 system to start the fax modems we added these lines to
inittab:

# Add fax lines and always ALWAYS run telinit q after making a change.
fax1:2345:respawn:/usr/sbin/faxgetty ttyS0
fax2:2345:respawn:/usr/sbin/faxgetty ttyS1


On the CentOS-6 host we did this, in accordance with the instructions
provided in the various README files and man pages.

# send
IA00:2345:respawn:/usr/bin/iaxmodem ttyIAX0
# receive
mo00:2345:respawn:/usr/sbin/faxgetty ttyIAX0
# send
IA01:2345:respawn:/usr/bin/iaxmodem ttyIAX1
# receive
mo01:2345:respawn:/usr/sbin/faxgetty ttyIAX1

However, when I do an init q the faxgetty instances do not start.  If
I run faxgetty from the command line in detached mode for each of them
(faxgetty -D ttyIAX0) then they do start.  The iaxmodem instances are
started from an init.d script as far as I can tell.  They appear and
disappear with service iaxmodem start and stop in any case and they
most certainly do not respawn if the service is stopped.

So, my question is: Does inittab have any use on el6 systems?  What is
its replacement? In other words, how do I accomplish what I am told to
do with respect to iaxmodem and faxgetty that formerly worked in
inittab and now evidently does not?

-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte  Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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


Re: [CentOS] 4 monitors with one graphics card and standard driver

2013-04-16 Thread Dale Dellutri
On Tue, Apr 16, 2013 at 2:47 PM, m.r...@5-cent.us wrote:

 Dale Dellutri wrote:
  I've just test an ATI FirePro 2460 graphics card on CentOS 6.4.  It
  connects 4 monitors.
  It worked with the standard radeon driver.  I was able to arrange the
  monitors into my preferred configuration (as a square array, 1 upper
  left, 2 lower left, 3 lower right, 4 upper right) simply by clicking
  System - Preferences - Display, and then moving the
  four monitor images.  This creates the file ~/.config/monitors.xml .
 snip
  I also tested two other cards: ATI FirePro 2450 and NVidia Quadro NVS
 420.
  For each of these cards, the BIOS shows the card in slot 1 as a PCI
  Bridge.
  lspci reports two identical video cards at 03:00.0 and 04:00.0.
  Though it's easy to set up two screens properly, xinerama would probably
  be required in an xorg.conf to get all four screens working properly.

 Would you mind sending me your xorg.conf offlist? I *may* have found
 something in the one I've been handcrafting, but as my user is busy, I
 won't be able to try it out for a while, and would love to see what you
 did.


As I said, when I used the ATI FirePro 2460, there was NO xorg.conf
created or required.  I would have needed one for the ATI 2450 or the
NVidia NVS 420, but I never tried to create one.


 I'm still at the point of him having one monitor working fine, but the
 other comes up, not mirrored, but unreachable by keyboard or mouse.
 Looking at his old xorg.conf that worked with kmod-fglrx, and my own (an
 NVidia card) I realized they only have one Screen sectiuon, and a viewport
 on his (mine, of course, has twinview), so I've just edited his that way.


I suggest that you restart the machine without X (in run level 3), then as
root
do:
  # X -configure
which will write a new xorg.conf.new in the current directory.

But are you sure the problem is in the xorg.conf?  What does System -
Preferences - Display show?

-- 
Dale Dellutri
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 4 monitors with one graphics card and standard driver

2013-04-16 Thread m . roth
Dale Dellutri wrote:
 On Tue, Apr 16, 2013 at 2:47 PM, m.r...@5-cent.us wrote:

 Dale Dellutri wrote:
  I've just test an ATI FirePro 2460 graphics card on CentOS 6.4.  It
  connects 4 monitors.
  It worked with the standard radeon driver.  I was able to arrange the
  monitors into my preferred configuration (as a square array, 1 upper
  left, 2 lower left, 3 lower right, 4 upper right) simply by clicking
  System - Preferences - Display, and then moving the
  four monitor images.  This creates the file ~/.config/monitors.xml .
 snip
  I also tested two other cards: ATI FirePro 2450 and NVidia Quadro NVS
 420. For each of these cards, the BIOS shows the card in slot 1 as a
  PCI Bridge.lspci reports two identical video cards at 03:00.0 and
04:00.0.
  Though it's easy to set up two screens properly, xinerama would
  probably be required in an xorg.conf to get all four screens working
  properly.

 Would you mind sending me your xorg.conf offlist? I *may* have found
 something in the one I've been handcrafting, but as my user is busy, I
 won't be able to try it out for a while, and would love to see what you
 did.

 I'm still at the point of him having one monitor working fine, but the
 other comes up, not mirrored, but unreachable by keyboard or mouse.
 Looking at his old xorg.conf that worked with kmod-fglrx, and my own (an
 NVidia card) I realized they only have one Screen sectiuon, and a
 viewport on his (mine, of course, has twinview), so I've just edited his
 that way.

 I suggest that you restart the machine without X (in run level 3), then as
 root
 do:
   # X -configure
 which will write a new xorg.conf.new in the current directory.

Tried that. It fails. Tried no xorg.conf, no X.

 But are you sure the problem is in the xorg.conf?  What does System -
 Preferences - Display show?

That's the fun one: it shows *one* monitor. I think I mentioned, xrandr
shows 1, also. It *also* describes it as DisplayPort-0, though it doesn't
like me using DisplayPort-0 for output, and I can't find what the output
name *is*. But if I say xrandr --screen 1, it shows me DisplayPort-1.

   mark

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


Re: [CentOS] 4 monitors with one graphics card and standard driver

2013-04-16 Thread m . roth
Ok, I'm almost there. I found a typo in my xorg.conf - actually, I had
copies one from someone out there that said it worked. Fixing that, in the
ServerLayout section, and I've now got the two screens, side by side, and
reachable. My two remaining problems: first, if I scroll around, it
appears as though X thinks that the screen is bigger than the monitor, and
it moves visible off the top of the monitor, leaving an L of black. The
other is, if I log in as root, and try to use System-Display, it tells me
RandR is disabled; meanwhile, in /var/log/Xorg.0.log, there are the two
entries, one for each displayport, that say ignore the following randr
disabled message

 mark

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


Re: [CentOS] inittab - huh what's it good for?

2013-04-16 Thread Michael H. Warfield
On Tue, 2013-04-16 at 16:18 -0400, James B. Byrne wrote:
 We run a CentOS-5 based hylafax server with external serial modems. We
 are transitioning to an Asterisk system using IAXmodem running on
 CentOS-6.

 On the CentOS-5 system to start the fax modems we added these lines to
 inittab:

 # Add fax lines and always ALWAYS run telinit q after making a change.
 fax1:2345:respawn:/usr/sbin/faxgetty ttyS0
 fax2:2345:respawn:/usr/sbin/faxgetty ttyS1


 On the CentOS-6 host we did this, in accordance with the instructions
 provided in the various README files and man pages.

 # send
 IA00:2345:respawn:/usr/bin/iaxmodem ttyIAX0
 # receive
 mo00:2345:respawn:/usr/sbin/faxgetty ttyIAX0
 # send
 IA01:2345:respawn:/usr/bin/iaxmodem ttyIAX1
 # receive
 mo01:2345:respawn:/usr/sbin/faxgetty ttyIAX1

 However, when I do an init q the faxgetty instances do not start.  If
 I run faxgetty from the command line in detached mode for each of them
 (faxgetty -D ttyIAX0) then they do start.  The iaxmodem instances are
 started from an init.d script as far as I can tell.  They appear and
 disappear with service iaxmodem start and stop in any case and they
 most certainly do not respawn if the service is stopped.

 So, my question is: Does inittab have any use on el6 systems?  What is
 its replacement? In other words, how do I accomplish what I am told to
 do with respect to iaxmodem and faxgetty that formerly worked in
 inittab and now evidently does not?

What you've described above works with CenOS 5 running sysv-init.  It
doesn't work with CentOS 6 because sysv-init has been replaced by
upstart.  That, in turn, will end up being replaced by systemd when 7
eventually comes out.  About the only thing that /etc/inittab is used
for under upstart or systemd is for the initial run level.  You might
want to read up on the upstart documentation and look at the contents of
the /etc/init directory.  The /etc/init.d directory contains the
sysv-init init scripts.  The /etc/init directory (no .d) has
configuration files for upstart.  Upstart can start sysv services and
run sysv-init style init scripts as well.

 -- 
 ***  E-Mail is NOT a SECURE channel  ***
 James B. Byrnemailto:byrn...@harte-lyne.ca
 Harte  Lyne Limited  http://www.harte-lyne.ca
 9 Brockley Drive  vox: +1 905 561 1241
 Hamilton, Ontario fax: +1 905 561 0757
 Canada  L8E 3C3

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  m...@wittsend.com
   /\/\|=mhw=|\/\/  | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9  | An optimist believes we live in the best of all
 PGP Key: 0x674627FF| possible worlds.  A pessimist is sure of it!


signature.asc
Description: This is a digitally signed message part
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos