logport-furlfile isn't always created

[Brian Warner]

The new Tub.setOption("logport-furlfile", "logport.furl") control doesn't always create the named file. It records the filename, but only populates it if/when anyone calls Tub.getLogPort() or Tub.getLogPortFURL() . As a result, you can't use flogtool tail on the application unless/until someone makes those calls.

I wrote it that way because it was a tiny nuisance to do the registerReference at the correct time, and because I thought that the logpublisher was enough. But now I'm looking at an application that has flog events I'd like to follow, and I have no easy way to get at them.

Either we need to declare that the application needs to make one of these calls after setLocation() is ready, or we need to find a way to auto-register this file inside the Tub at the right time.

[Brian Warner]

hm, yeah, the problem is that from inside the Tub, we don't really know when the app has finished doing all the setLocations that it wants.

[Brian Warner]

Ah, but really you only do setLocation once, since it takes a tuple of hints. So we can create the furlfile when setLocation() is called. Fixed, in [7453c3e2b7042667d4b03b6124cc5d3c1fc61260].