----- Original Message -----
> I forgot to mention that there is some qa fallout associated with new
> messages in the pmcd log that I still need to address.
I've added a new diagnostic flag to guard these (and future discovery
related info/debug messages). Just running rest of QA now, 243 seems
to have failed, unrelated to above (first pmcd did not start so second
pmcd didn't get the expected bind(2) failure?) ... as has 283, similar
issue - pmcd not starting. Tests on-going, so others might crop up as
well yet - ~50% done.
Given these issues, we should probably add a pmcd command line option
to disable the server advertising code - just in case.
I've also cleaned up those small consistency issues - see f7e39ca51 -
and plan to merge it all shortly into dev, we'll need those remaining
failure cases sorted out next I guess.
cheers.
--
Nathan
283.out.bad
Description: Binary data
243.out.bad
Description: Binary data
|