Comment 9 for bug 1786261

@ehoover; great isolation! that's absolutely it

I too noticed it hangs in several other ways randomly.

One other example I had not mentioned was failing here:
{{{
Aug 20 09:02:49 fermmy charon[3698]: 14[IKE] maximum IKE_SA lifetime 56591s
Aug 20 09:02:49 fermmy charon[3698]: 14[IKE] processing INTERNAL_IP4_ADDRESS attribute
Aug 20 09:02:49 fermmy charon[3698]: 14[IKE] processing INTERNAL_IP4_DNS attribute
<<HANGS>>
}}}

During this state:
{{{
$ ps wuaxxx | grep host
root 8526 0.0 0.0 187628 8792 ? Sl 09:02 0:00 host -t soa local.
}}}

Then:
{{{
$ sudo killall host
}}}

tada: (this immediately followed log message then appears)
{{{
Aug 20 09:04:24 fermmy charon[3698]: 10[IKE] removing DNS server 192.168.194.20 via resolvconf
Aug 20 09:04:24 fermmy charon[3698]: 14[IKE] installing DNS server 192.168.194.20 via resolvconf
Aug 20 09:04:24 fermmy charon[3698]: 14[IKE] processing INTERNAL_IP4_DNS attribute
Aug 20 09:04:24 fermmy charon[3698]: 14[IKE] installing DNS server 192.168.196.20 via resolvconf
Aug 20 09:04:24 fermmy charon[3698]: 14[IKE] installing new virtual IP 192.168.130.4
Aug 20 09:04:24 fermmy charon[3698]: 14[IKE] CHILD_SA wtlsecondary{72} established with SPIs c557c437_i 9ae567d1_o and TS 192.168.130.4/32 === 10.0.0.0/8 172.16.0.0/12 192.168.128.0/17
Aug 20 09:04:24 fermmy charon[3698]: 14[IKE] CHILD_SA wtlsecondary{72} established with SPIs c557c437_i 9ae567d1_o and TS 192.168.130.4/32 === 10.0.0.0/8 172.16.0.0/12 192.168.128.0/17
}}}

it's definitely resolvconf related :( -- and as you suggest

we should move this defect to the appropriate sub-category then