Hi Anurag and all, GUI bits are at: /net/jdsserv.ireland/scratch/month/darrenk/NWAM_Manager_Phase_1/i386/rc6 /net/jdsserv.ireland/scratch/month/darrenk/NWAM_Manager_Phase_1/sparc/rc6
That 'first time no notifications' issue looks a Gnome gconf issue. To work around it, after install the GUI packages run 'pkill gconfd-2' or re-login to Gnome. Thanks, lin Anurag S. Maskey wrote: > Lin, > > We are doing RC6 build. There are libnwam changes so the GUI has to > be rebuilt, plus you have quite a few bug fixes waiting to go out. > Could you do a gui build and let me know where the bits are. The ON > bits are at: > > /net/zhadum.east/export/ws/am223141/nwam1-build > /net/trigati.east/export/build/am223141/nwam1-build > > Thanks, > Anurag > > > -------- Original Message -------- > Subject: Re: RC6 > Date: Wed, 18 Nov 2009 10:15:18 +0000 > From: Alan Maguire <Alan.Maguire at Sun.COM> > To: Michael Hunter <Michael.Hunter at Sun.COM> > CC: Renee Danson Sommerfeld <renee.sommerfeld at sun.com>, > Anurag.Maskey at Sun.COM > References: <20091118004023.GA248397 at jurassic-x4600.Eng.Sun.COM> > <20091118015457.00002dc5 at sun.com> > > > > Michael Hunter wrote: >> On Tue, 17 Nov 2009 16:40:23 -0800 >> Renee Danson Sommerfeld <renee.sommerfeld at sun.com> wrote: >> >> >>> I think we've completed execution of all the tests, and have filed >>> all the bugs we're currently aware of. The only P3 is the one >>> Michael filed from his stress testing, where nwamd grew by ~3MB >>> over many refreshes. >>> >> >> That was about an hour of refreshes with one about every 4 seconds so >> about 900 refreshes. This is unbounded. I kept the test running and >> nwamd just kept growing. This shouldn't be hard to figure out. And its >> really artificial. Also you can't reproduce this unless you restart >> svc.configd on a regular basis. It grows a lot quicker and ultimately >> turns the machine into a blinking warm brick :) >> >> >>> We've also fixed some pretty significant bugs since RC5. >>> >>> My inclination is to say let's go on RC6, with the current gate. >>> >>> Any objections? >>> >> >> Not from me. >> >> > me neither. I do have some stuff in the pipeline - > where we drop object locks during scan/connect - > but it touches enough critical paths that I'd like to > be really sure it's safe before codereview/integration. > I estimate another day coding, and a couple of days > testing, but since it's impact on users is minimal - > "nwamadm list" is more responsive as a consequence - > it shouldn't hold anything else up. > > One thing we do need is a new GUI build against the > latest libnwam.h. I don't think I've seen one though. > > Alan >
