search for: stangely

On 01/24/2017 11:16 AM, Kevin Stange wrote: > On 01/24/2017 09:10 AM, Konrad Rzeszutek Wilk wrote: >> On Tue, Jan 24, 2017 at 09:29:39PM +0800, -=X.L.O.R.D=- wrote: >>> Kevin Stange, >>> It can be either kernel or update the NIC driver or firmware of the NIC >>> card. Hope that helps! >>> >>> Xlord >>> -----Original Message-----

On 01/26/2017 09:32 AM, Johnny Hughes wrote: > On 01/25/2017 11:49 AM, Kevin Stange wrote: >> On 01/24/2017 11:16 AM, Kevin Stange wrote: >>> On 01/24/2017 09:10 AM, Konrad Rzeszutek Wilk wrote: >>>> On Tue, Jan 24, 2017 at 09:29:39PM +0800, -=X.L.O.R.D=- wrote: >>>>> Kevin Stange, >>>>> It can be either kernel or update the NIC driver or

On 11/02/17 06:29, Kevin Stange wrote: > On 01/30/2017 06:41 PM, Kevin Stange wrote: >> On 01/30/2017 06:12 PM, Adi Pircalabu wrote: >>> On 31/01/17 10:49, Kevin Stange wrote: >>>> You said 3.x kernels specifically. The kernel on Xen Made Easy now is a >>>> 4.4 kernel. Any chance you have tested with that one? >>> >>> Not yet, however

On 09/06/2017 05:21 PM, Kevin Stange wrote: > On 09/06/2017 08:40 AM, Johnny Hughes wrote: >> On 09/05/2017 02:26 PM, Kevin Stange wrote: >>> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>>> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>>>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>>>> On 09/01/2017 02:41 PM, Kevin Stange wrote:

On 01/26/2017 02:08 PM, Kevin Stange wrote: > On 01/26/2017 09:35 AM, Johnny Hughes wrote: >> On 01/26/2017 09:32 AM, Johnny Hughes wrote: >>> On 01/25/2017 11:49 AM, Kevin Stange wrote: >>>> On 01/24/2017 11:16 AM, Kevin Stange wrote: >>>>> On 01/24/2017 09:10 AM, Konrad Rzeszutek Wilk wrote: >>>>>> On Tue, Jan 24, 2017 at 09:29:39PM

On 01/30/2017 06:12 PM, Adi Pircalabu wrote: > On 31/01/17 10:49, Kevin Stange wrote: >> You said 3.x kernels specifically. The kernel on Xen Made Easy now is a >> 4.4 kernel. Any chance you have tested with that one? > > Not yet, however the future Xen nodes we'll deploy will run CentOS 7 and > Xen with kernel 4.4. I'll keep you (and others here) posted on my

On Tue, Jan 24, 2017 at 09:29:39PM +0800, -=X.L.O.R.D=- wrote: > Kevin Stange, > It can be either kernel or update the NIC driver or firmware of the NIC > card. Hope that helps! > > Xlord > -----Original Message----- > From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Kevin > Stange > Sent: Tuesday, January 24, 2017 1:04 AM > To: centos-virt

On 09/05/2017 02:26 PM, Kevin Stange wrote: > On 09/04/2017 05:27 PM, Johnny Hughes wrote: >> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>> On 09/01/2017 02:41 PM, Kevin Stange wrote: >>>>> On 08/31/2017 07:50 AM, PJ Welsh wrote: >>>>>> A recently created and fully functional CentOS

Environment: CentOS 4.2 (RHES4 clone) Ruby 1.8.4 Rails 1.0 I am having a small difficulty with case sensitive matching in some ruby code: f_nam_re = Regexp.new(f_nam_re_s,"x") produces these test results: The passed regexp: ^QPCCCMR[[:digit:]]$ The regexp used is: /^QPCCCMR[[:digit:]]$/i $= is false qpcccmr1 matches QPCCCMR1 matches QPCCMMR1 does not match qpCCCMR1 matches QPCCCMRC

Tom Blackwell wrote: >... >I summarized this to myself as "computed subscripts need explicit >rounding in R, but not in S". Here's the sample code which gave >me different results with R than with Splus. I no longer have >Splus available, so I can't check it again. >look <- (10 * seq(14)) - 76 >chk.1 <- seq(1420)[ 10 * (73.1 + look) ] #

Greetings, CentOS. After up2dating one of the corporate mail servers to CentOS 4.4 (was CentOS 4.2) and upgrading kernel to kernel-smp-2.6.9-42.0.3.EL, the following kernel messages started to appear in syslog: [root at gamma ~]# dmesg ........... ...CUT..... ........... lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected

Hi all, I have a SPA 1001 with DTMF set to auto. A sip.conf peer with codec alaw, ulaw, g729. I have dtmf=inband as this peer was only supporting alaw/ulaw. They just add g729, it's a GW to landline phones. A call passing through this peer give me "WARNING Inband not supported with g729, use RFC2833 instead". The call is connecting and DTMF is working. Now I'm coming back

Does anyone know what the following error means, and what I can do to fix it?? [root@trouble openldap]# ldapadd -D "cn=root,o=smb,dc=picotech,dc=net" -W Enter LDAP Password: ldap_sasl_interactive_bind_s: No such attribute ------------- Jeffrey D. Means CIO for PicoTech Ft. Collins, Colorado -------------- next part -------------- HTML attachment scrubbed and removed

I posted a rather lengthy message a few weeks ago. Andrew B and Jerry both responded with indications of furthers investigation required....i was wondering if anyone found anything strange because I've had to go back to 2.2.5 to support those clients and with a bit of fear of potential strange behaviour in my XP clients. Don't wish to be a pest, but you guys have done so much for our

Hi I am having strange problem using samba share using Linux file managers like nautilus and konquers. I can successfully mount samba share using smb://mnt/c but every time it asks for password. When I click on one folder and come back it again asks for password and that is very annoying. Pls help me Komal

Hi! I''m developing an application with Rails 1.2.6 and I''ve facing a weird problem. In a form, I''m using link_to_function that is aggregating a :partial, the code is as follows: <table> <thead> <tr> <th>Marca</th> <th>Porcentaje</th> <th>Objetivo Mensual</th>

On 03/27/2017 04:03 PM, Kevin Stange wrote: > On 03/25/2017 02:35 PM, Sarah Newman wrote: >> On 03/16/2017 04:22 PM, Kevin Stange wrote: >> >>>> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >>>> server has yet had a NIC issue, with some being up almost a full month. >>>> It looks promising! (I'm knocking on all the

On 03/16/2017 04:22 PM, Kevin Stange wrote: >> I still can't rest assured the NIC issue is fixed, but no 4.4 or 4.9 >> server has yet had a NIC issue, with some being up almost a full month. >> It looks promising! (I'm knocking on all the wood everywhere, though.) > > I'm ready to call this conclusive. The problems I was having across the > board seemed to

Have you tried to eliminate all power management features all over? Are the devices connected to the same network infrastructure? There has to be something common. I've been using Intel NICs with Xen/CentOS for ages with no issues. Karel On 27.1.2017 02:57, Kevin Stange wrote: > On 01/26/2017 02:08 PM, Kevin Stange wrote: >> On 01/26/2017 09:35 AM, Johnny Hughes wrote:

On 14-09-2017 20:57, Adi Pircalabu wrote: > On 08-09-2017 6:17, Kevin Stange wrote: >> On 09/06/2017 05:21 PM, Kevin Stange wrote: >>> On 09/06/2017 08:40 AM, Johnny Hughes wrote: >>>> On 09/05/2017 02:26 PM, Kevin Stange wrote: >>>>> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>>>>> On 09/04/2017 03:59 PM, Kevin Stange wrote: