8:28 p.m.
On 4/26/19 12:08 PM, JH wrote:
> BTW: you've used ".conf" suffix but the document
mandates ".config".
Yeap, I sent another email to correct my typo.
You can see what ConnMan thinks of your config file by
# ./connmand -n -d src/config.c
connmand[11316]: Adding configuration test
connmand[11316]: Type of the configured service is missing for group
service_home
connmand[11316]: Config file /var/lib/connman/test.config does not
contain any configuration that can be provisioned!
connmand[11316]: Removing configuration .#test
connmand[11316]: Adding configuration .#test
connmand[11316]: Removing configuration test
connmand[11316]: Adding configuration test
connmand[11316]: Type of the configured service is missing for group
service_home
> Regardless, connman v1.36 certainly doesn't follow the file
structure
> described in doc/config-format.txt. After manually provisioning my
> dial-up connection I can see directories:
>
> /var/lib/connman/cellular_248030054743345_context1/
> /var/lib/connman/ethernet_00e04c2154c3_cable/
>
> Both contain two files "data" and "settings". Here's a
"settings" file,
> which does what you're looking to do - start the dial-up on boot.
That is the normal connman set up, I think what Daniel and document
said was if you deploy a file ${name}.config to /var/lib/connman, the
connman daemon will be notified and auto connect those services
without manual configuration that what embedded systems require. But
the auto connect feature does not seem work, Daniel is busy.
Daniel, if you could let me know that is the issue to cause auto
connect not working, where to look, I will try it.
I understand you have at least two problems which you try to solve. For
the provisioning the above trick might help.
Can you post the output from the list-services script?
Thanks,
Daniel