Hi,
On 01/14/2013 02:20 PM, Daniel Wagner wrote:
On 14.01.2013 14:08, Daniel Wagner wrote:
when something blocks:
connmanMonitor::servicesChanged
START: getServices !
getServices duration: 0.00296497344971
START: getServices !
getServices duration: 0.00302910804749
START: getServices !
getServices duration: 0.00310301780701
connmanMonitor::managerPropertyChanged
connmanMonitor::propertyChanged
connmanMonitor::managerPropertyChanged
connmanMonitor::propertyChanged
connmanMonitor::servicesChanged
START: getServices !
getServices duration: 0.00301790237427
START: getServices !
getServices duration: 0.00303387641907
START: getServices !
getServices duration: 6.37309789658
It seems that those timeout above are corresponding to the
append_nameservers() log entries
connmand[6082]: src/service.c:append_ipv4() ipv4 0x1be1210 state online
connmand[6082]: src/ipconfig.c:__connman_ipconfig_append_ipv4()
connmand[6082]: src/ipconfig.c:__connman_ipconfig_append_ipv4config()
connmand[6082]: src/service.c:append_ipv6() ipv6 0x1be1300 state idle
connmand[6082]: src/ipconfig.c:__connman_ipconfig_append_ipv6config()
connmand[6082]: src/service.c:append_nameservers() 0x1be6090
connmand[6082]: src/service.c:append_nameservers() servers[0] 192.168.100.4
connmand[6082]: src/service.c:append_nameservers() servers[1] 192.168.100.1
connmand[6082]: src/storage.c:storage_load() Loading /var/lib/connman/settings
connmand[6082]: src/service.c:append_proxy()
connmand[6082]: src/service.c:append_provider() 0x1bdc520 (nil)
Could it be that we block there?
After some more testing it is clear that ConnMan is working fine.
while sleep 1 ; do time connmanctrl services ; done
The Python script was running and in parallel the avove line did never
block.
And whenever I saw the getServices() blockin, connmanctl just keept
working fine.
From that I would say the problem is on the Python script side.
cheers,
daniel
_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
