Re: Improving loadparm design to fix bug in configuration reloading

2009-01-30 Thread Matt McCutchen
On Fri, 2009-01-16 at 22:36 -0500, Matt McCutchen wrote: > On Fri, 2009-01-16 at 19:23 -0800, Wayne Davison wrote: > > On Wed, Jan 14, 2009 at 02:25:33AM -0500, Matt McCutchen wrote: > > > I think I'll take the opportunity to improve the design a bit by > > > actually adding a section structure re

Re: Improving loadparm design to fix bug in configuration reloading

2009-01-16 Thread Matt McCutchen
On Fri, 2009-01-16 at 19:23 -0800, Wayne Davison wrote: > On Wed, Jan 14, 2009 at 02:25:33AM -0500, Matt McCutchen wrote: > > I think I'll take the opportunity to improve the design a bit by > > actually adding a section structure representing the global values of > > section parameters to the glob

Re: Improving loadparm design to fix bug in configuration reloading

2009-01-16 Thread Wayne Davison
On Wed, Jan 14, 2009 at 02:25:33AM -0500, Matt McCutchen wrote: > I think I'll take the opportunity to improve the design a bit by > actually adding a section structure representing the global values of > section parameters to the global structure I was thinking we could get rid of the big, must-k

Improving loadparm design to fix bug in configuration reloading

2009-01-13 Thread Matt McCutchen
While I was working on the avoid-reverse-lookup patches, I found a flaw in the daemon's behavior of reloading the configuration on each connection. If I remove a module parameter (in my case, "hosts allow") from the global section, the removal does not take effect. This is because loadparm.c does