-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
maybe file a bugreport for libvirt?
https://bugzilla.redhat.com/enter_bug.cgi?product=Virtualization%20Toolscomponent=libvirt
Am 18.09.2013 19:18, schrieb C. L. Martinez:
On Sun, Sep 15, 2013 at 5:07 PM, carlopmart carlopm...@gmail.com
wrote:
On Wed, Sep 18, 2013 at 8:34 PM, David Hackl i...@dh-online.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
maybe file a bugreport for libvirt?
https://bugzilla.redhat.com/enter_bug.cgi?product=Virtualization%20Toolscomponent=libvirt
uhmm I don't think I can do that. Problem is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
well, it seems like your problem is libvirt based and not xen based.
libvirt uses redhat bugzilla for bugtracking.
btw: redhat develops a big part of libvirt...
Am 18.09.2013 22:50, schrieb C. L. Martinez:
On Wed, Sep 18, 2013 at 8:34 PM, David
Correct, my problem is with libvirt but only when I use xen as a
hypervisor, not when I use kvm ...
When you setup a new vm using libvirt under a RHEL 6.x host, you don't
see Xen hypervisor as an option ... I doubt that Redhat accepts this
as a problem with their libvirt package ... but maybe I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
the bugtracker is for all libvirt bugs, not specific rhel bugs...
that's the official bugtracker for the libvirt project.
so of course you can use that bugtracker...
Am 18.09.2013 23:09, schrieb C. L. Martinez:
Correct, my problem is with libvirt
hola en el log del servidor proxy he observado que hay accesos extraños como:
http://hghhbyuigfhie/
y como son varios ocasiona que el proxy trabaje lento.
les ha pasado?
saludos
___
CentOS-es mailing list
CentOS-es@centos.org
On 09/18/2013 05:44 AM, César C. wrote:
hola en el log del servidor proxy he observado que hay accesos extraños como:
http://hghhbyuigfhie/
y como son varios ocasiona que el proxy trabaje lento.
les ha pasado?
es una máquina con un troyano, acércate a ella y le revisas.
Si no está a tu
hola
¿sabes que troyano es?
Date: Wed, 18 Sep 2013 06:46:40 -0500
From: cen...@ecualinux.com
To: centos-es@centos.org
Subject: Re: [CentOS-es] trafico anomalo a proxy
On 09/18/2013 05:44 AM, César C. wrote:
hola en el log del servidor proxy he observado que hay accesos extraños
Eso también me pasaba en el instituto, busca en el log del squid, el ip de
la maquina que genera el trafico, si las ips son dinámicas si tienes un
rollo.
Cuando hayas detectado que maquina dale format, ese virus solo se activa a
ciertas horas.
Saludos,
PD. no recuerdo que virus es.
*Aland
Good morning!
On a CentOS 6.4 / 64 bit server I have
installed the watchdog 5.5 package.
The rpm -qi watchdog states:
The watchdog program can be used as a powerful software watchdog
daemon or may be alternately used with a hardware watchdog device such
as the IPMI hardware watchdog driver
On 09/18/2013 03:57 AM, Alexander Farber wrote:
Good morning!
On a CentOS 6.4 / 64 bit server I have
installed the watchdog 5.5 package.
The rpm -qi watchdog states:
The watchdog program can be used as a powerful software watchdog
daemon or may be alternately used with a hardware watchdog
On 09/17/2013 11:27 PM, Robert Arkiletian wrote:
Latest chromium-el6 at
http://people.centos.org/hughesjr/chromium/6/x86_64/RPMS/
is
chromium-28.0.1500.95-213514.x86_64.rpm
but latest chromium stable is 29.0.1547.xx
wondering if there are any problems building version 29?
Yes, there are
On Wed, Sep 18, 2013 at 05:41:43AM -0500, Johnny Hughes wrote:
On 09/17/2013 11:27 PM, Robert Arkiletian wrote:
Latest chromium-el6 at
http://people.centos.org/hughesjr/chromium/6/x86_64/RPMS/
is
chromium-28.0.1500.95-213514.x86_64.rpm
but latest chromium stable is 29.0.1547.xx
Hello Steve,
yes, I have that device:
# ll /dev/watchdog
crw-rw 1 root root 10, 130 Sep 17 23:21 /dev/watchdog
# ps uawwx|grep w[a]tchdog
root 6 0.0 0.0 0 0 ?SSep17 0:00 [watchdog/0]
root10 0.0 0.0 0 0 ?SSep17 0:00
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
We have a very old MS-Windows domain running on a Win2K advanced server.
After the most recent update to Samba it appears that we can no longer connect
to shares on that system from our CentOS-6.4 workstations. Is this a known
problem or configuration issue that we need to address through local
On 09/18/2013 07:20 AM, Alexander Farber wrote:
Hello Steve,
yes, I have that device:
# ll /dev/watchdog
crw-rw 1 root root 10, 130 Sep 17 23:21 /dev/watchdog
# ps uawwx|grep w[a]tchdog
root 6 0.0 0.0 0 0 ?SSep17 0:00 [watchdog/0]
root10 0.0
Am 18.09.2013 14:55, schrieb James B. Byrne:
We have a very old MS-Windows domain running on a Win2K advanced server.
After the most recent update to Samba it appears that we can no longer connect
to shares on that system from our CentOS-6.4 workstations. Is this a known
problem or
On 2013-09-18 6:41 AM, Johnny Hughes wrote:
http://www.tecmint.com/install-google-chrome-on-redhat-centos-fedora-linux/
That page requests credentials, even from google's cache.
___
CentOS mailing list
CentOS@centos.org
If you keep on canceling the auth dialog it will eventually load from
Google's cache, minus the images. The main download is a script that
does the package copy. I'll have a chance to try it in about an hour.
Johnny, thanks for your efforts in getting this to work.
2013/9/18 Darr247
try asking from samba mailinglist. Your Windows system is tool old, sorry :(
--
Eero
2013/9/18 James B. Byrne byrn...@harte-lyne.ca
We have a very old MS-Windows domain running on a Win2K advanced server.
After the most recent update to Samba it appears that we can no longer
connect
to
I'm skeptical about a long term solution involving a script that
copies binaries from Fedora distribution. I would prefer a solution
which incorporates the newer devtools from Tru.
On Wed, Sep 18, 2013 at 2:19 PM, Kwan Lowe kwan.l...@gmail.com wrote:
If you keep on canceling the auth dialog it
We have a pretty standard installation of CentOS 6.4 on our
workstations. We've been running into issues where kdm crashes every
once in a while when someone tries to log in on the console. The only
way to recover when it happens seems to be to restart kdm (kill -HUP
`pgrep -f /usr/bin/kdm`)
23 matches
Mail list logo