Re: FreeBSD: syslog-ng: I/O error occurred while writing; fd='xx', error='No buffer space available (yy)'

2012-03-23 Thread Traiano Welcome
Hi John On 22/03/2012 14:16, "John Baldwin" wrote: >On Thursday, March 22, 2012 6:03:21 am Traiano Welcome wrote: >> Hi List >> >> I've been seeing the following in the messages log of my freebsd syslog >> server for quite some time now: >> >> --- >> Mar 20 12:19:12 syslog2 syslog-ng[35313]

Re: ifconfig meshforward command bug

2012-03-23 Thread Monthadar Al Jaberi
On Thu, Mar 22, 2012 at 10:23 PM, Adrian Chadd wrote: > I've fixed the one that Monthadar has submitted. > > Monthadar, would you mind reviewing the rest of the mesh commands and > see which others need fixing? from what I can see the bug is for flags that we can either turn on or off. Another on

Re: ifconfig meshforward command bug

2012-03-23 Thread Monthadar Al Jaberi
On Thu, Mar 22, 2012 at 7:56 PM, Adrian Chadd wrote: > On 22 March 2012 11:56, Adrian Chadd wrote: >> On 22 March 2012 11:28, Bernhard Schmidt wrote: >> >>> Seems about right, those declared with DEF_CMD() should use d. >> >> Shall I commit this? > > .. a lot of these mesh functions use DECL_CMD

Re: FreeBSD: syslog-ng: I/O error occurred while writing; fd='xx', error='No buffer space available (yy)'

2012-03-23 Thread John Baldwin
On Thursday, March 22, 2012 11:00:35 am Traiano Welcome wrote: > Hi John > > > > On 22/03/2012 14:16, "John Baldwin" wrote: > > >On Thursday, March 22, 2012 6:03:21 am Traiano Welcome wrote: > >> Hi List > >> > >> I've been seeing the following in the messages log of my freebsd syslog > >> se

Re: FreeBSD: syslog-ng: I/O error occurred while writing; fd='xx', error='No buffer space available (yy)'

2012-03-23 Thread Traiano Welcome
Hi John On 22/03/2012 19:49, "John Baldwin" wrote: >On Thursday, March 22, 2012 11:00:35 am Traiano Welcome wrote: >> Hi John >> >> >> >> On 22/03/2012 14:16, "John Baldwin" wrote: >> >> >On Thursday, March 22, 2012 6:03:21 am Traiano Welcome wrote: >> >> Hi List >> >> >> >> I've been s

Re: Intel 82574L interface wedging - em7.3.2/8.2-STABLE

2012-03-23 Thread Mike Tancsa
On 3/20/2012 2:57 PM, John Baldwin wrote: >>> TX when link becomes active. I've also updated it to fix resume for em >>> and igb to DTRT when buf_ring is used, and to not include old-style start >>> routines at all when using multiq. It is at >>> http://www.freebsd.org/~jhb/patches/e1000_txeof2.p

Re: ifconfig meshforward command bug

2012-03-23 Thread Bernhard Schmidt
On Friday 23 March 2012 10:11:07 Monthadar Al Jaberi wrote: > On Thu, Mar 22, 2012 at 10:23 PM, Adrian Chadd wrote: > > I've fixed the one that Monthadar has submitted. > > > > Monthadar, would you mind reviewing the rest of the mesh commands and > > see which others need fixing? > > from what I

Re: Intel 82574L interface wedging - em7.3.2/8.2-STABLE

2012-03-23 Thread Jason Wolfe
On Fri, Mar 23, 2012 at 11:09 AM, Mike Tancsa wrote: > On 3/20/2012 2:57 PM, John Baldwin wrote: TX when link becomes active.  I've also updated it to fix resume for em and igb to DTRT when buf_ring is used, and to not include old-style start routines at all when using multiq.  It i

Re: Intel 82574L interface wedging - em7.3.2/8.2-STABLE

2012-03-23 Thread John Baldwin
On Friday, March 23, 2012 2:09:29 pm Mike Tancsa wrote: > On 3/20/2012 2:57 PM, John Baldwin wrote: > >>> TX when link becomes active. I've also updated it to fix resume for em > >>> and igb to DTRT when buf_ring is used, and to not include old-style start > >>> routines at all when using multiq.