On Tue, 15 Sep 2009 18:19:41 -0400, Jeff Garzik <jeff@xxxxxxxxxx> wrote: > On 09/14/2009 02:15 PM, Pete Zaitcev wrote: > > On Wed, 09 Sep 2009 15:01:52 -0400, Jeff Garzik<jeff@xxxxxxxxxx> wrote: > > > >> though for uniformity, I lean towards thinking that the daemon should > >> always write a port file, regardless of whether the port was manually > >> specified or automatically bound. > > > > I have a better idea. Let's split PortFile from the enabling > > of auto ports. We can have<Port> to with a special string "auto", > > and let<PortFile> to be set when static port is configured. > > I think that's fair... I have posted tabled already, so we have all three in exactly the same, old scheme now. I'll patch it over. Not sure if I can make it compatible though... There may be another flag day. Sorry. I realized my folly when <PortFile>/dev/null</PortFile> appeared. Probably would've fixed it anyway. -- Pete -- To unsubscribe from this list: send the line "unsubscribe hail-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html