Re: sed problems on Solaris

2006-10-10 Thread Thomas Anders
Bruce Shaw wrote: > One problem may be with sed itself. Huh? The *whole* issue here is how to properly deal with sed limitations at configure time. > I routinely patch to Sun's recommendation, but somehow the sed patch was > missed on at least on of my development boxes. > > I had to add patch 1

Re: sed problems on Solaris

2006-10-10 Thread Bruce Shaw
One problem may be with sed itself. >> As a short-term fix, it would be possible to temporarily drop the >> above three lines from configure.in, and comment out the corresponding >> lines in agent/Makefile.in >Unfortunately configure seems to use hard-coded calls to 'sed' in >AC_OUTPUT, so I don'

Re: 5.4 Open Issues

2006-10-10 Thread Thomas Anders
Dave Shield wrote: > On 10/10/06, Thomas Anders <[EMAIL PROTECTED]> wrote: >>> 1) OpenBSD4 headers > >> Huh? We neither have openbsd3.h nor openbsd4.h, but just openbsd.h. > > OK - in that case, I don't understand the comment >"openbsd4 uses openbsd.h, and thus a lot of openbsd3 code > th

Re: 5.4 Open Issues

2006-10-10 Thread Dave Shield
On 10/10/06, Bruce Shaw <[EMAIL PROTECTED]> wrote: > >3) hrStorageIndexes > Locking the beginning of the disk entries into index 30 assumes nobody would > 'be stupid'/'is insane'/'has a server overworked' enough to have more than > 29 swap entries. That's not a good assumption. Agreed. One appr

Re: 5.4 Open Issues

2006-10-10 Thread Dave Shield
On 10/10/06, Thomas Anders <[EMAIL PROTECTED]> wrote: > > 1) OpenBSD4 headers > Huh? We neither have openbsd3.h nor openbsd4.h, but just openbsd.h. OK - in that case, I don't understand the comment "openbsd4 uses openbsd.h, and thus a lot of openbsd3 code that most likely works on openbsd4

Re: 5.4 Open Issues

2006-10-10 Thread Thomas Anders
Dave Shield wrote: > 1) OpenBSD4 headers > What would be the implications of adding >#include > to openbsd4.h? Huh? We neither have openbsd3.h nor openbsd4.h, but just openbsd.h. I think we should come to a consensus whether foobar42

RE: 5.4 Open Issues

2006-10-10 Thread Bruce Shaw
>3) hrStorageIndexes I'm happy with the current state (unsurprisingly!), though it's probably sensible to document the change. Any objections? Locking the beginning of the disk entries into index 30 assumes nobody would 'be stupid'/'is insane'/'has a server overworked' enough

Re: 5.4 Open Issues

2006-10-10 Thread Juergen Schoenwaelder
On Tue, Oct 10, 2006 at 08:15:29PM +0100, Dave Shield wrote: > R1) TCP notifications > This seems to be the biggy - at least it's the only entry > categorised red. > Do we agree that it needs to be fixed before release, or should it be > re-graded yellow. If it stays

Re: 5.4 Open Issues

2006-10-10 Thread Dave Shield
On 10/10/06, Dave Shield <[EMAIL PROTECTED]> wrote: > I offer the following list - complete with comments and strawman > proposals - for the purpose of stimulating debate: Argghh. I knew there was another issue I wanted to add: 11) Darwin build There have been reports of the HAL CPU

5.4 Open Issues

2006-10-10 Thread Dave Shield
I thought it might be worth trying to deal with (or at least come to some consensus on) the various open issues for 5.4 - so we can surprise Wes with a clean slate when he gets back from holiday. Well, a man can dream, can't he? I've already re-categorised a couple of entries as not really releva

Re: help attaching files to a bug

2006-10-10 Thread Robert Story
On Thu, 05 Oct 2006 08:05:24 -0700 Wes wrote: WH> > "PP" == Passera Pablo-APP writes: WH> WH> PP> I submitted a bug and I'm trying to upload the patch for it but I WH> PP> couldn't do it. I think it is because I submitted the patch as WH> PP> nobody. The attach file option is not there. Is t

Re: SNMPv3 - problem with auth/encr sessions with Perl module

2006-10-10 Thread ML
Dnia poniedziałek, 9 października 2006 18:58, ML napisał: > So, this looks like some Windows-specific issue - I had some time to > experiment and it not only fails to run properly using 5.3.1 "official" > version from windows installer, but also on my own, private build built > with MS VC++ Expres

Re: add multiple rows with 1 set - crash

2006-10-10 Thread Robert Story
On Tue, 10 Oct 2006 12:33:11 -0400 Robert wrote: RS> On Mon, 9 Oct 2006 15:10:44 +0100 Graeme wrote: RS> GW> Hi Robert, RS> GW> RS> GW> I can confirm that the patch you provided to row_merge.c fixes the RS> GW> problem of adding 2 rows to a table with 1 set. RS> GW> I notice that this hasn't yet b

Re: sed problems on Solaris

2006-10-10 Thread Robert Story
On Tue, 10 Oct 2006 17:05:53 +0100 Dave wrote: DS> Thomas & I have been discussing the problems with an over-long 'sed' DS> line breaking configure on the latest 5.4 code. Further DS> investigation shows that there are three substitutions which are DS> failing, resulting from the entries: DS> DS

Re: add multiple rows with 1 set - crash

2006-10-10 Thread Robert Story
On Mon, 9 Oct 2006 15:10:44 +0100 Graeme wrote: GW> Hi Robert, GW> GW> I can confirm that the patch you provided to row_merge.c fixes the GW> problem of adding 2 rows to a table with 1 set. GW> I notice that this hasn't yet been merged into the main net-snmp code GW> yet. Do you plan on adding th

Re: sed problems on Solaris

2006-10-10 Thread Thomas Anders
Dave Shield wrote: > As a short-term fix, it would be possible to temporarily drop the > above three lines from configure.in, and comment out the corresponding > lines in agent/Makefile.in Unfortunately configure seems to use hard-coded calls to 'sed' in AC_OUTPUT, so I don't see a way to have con

sed problems on Solaris

2006-10-10 Thread Dave Shield
Thomas & I have been discussing the problems with an over-long 'sed' line breaking configure on the latest 5.4 code. Further investigation shows that there are three substitutions which are failing, resulting from the entries: AC_SUBST( module_list_h) AC_SUBST( mib_module_list_h) AC_

Re: rfc: Solaris udp-mib/tcp-mib rewrites in 5.4?

2006-10-10 Thread Dave Shield
On 09/10/06, Thomas Anders <[EMAIL PROTECTED]> wrote: > Sun has recently submitted patches to add the missing Solaris bits to the > udp-mib and tcp-mib rewrites that only support(ed) Linux, initially. > > Although it's probably to be considered new code rather than bug fixes and > we're > in preX