connmand doesn't autostart

[jls]

Hi
I have connman onboot, but the connmand process isn't autostarted.
If I manunally execute:

Code: [Select]

sudo /usr/local/tce.installed/connman
I get:

Code: [Select]

initctl: Impossibile connettersi a Upstart: Failed to connect to socket /com/ubuntu/upstart: Connessione rifiutata
 * Starting Connection Manager
   ...done.
Can't exec "/sbin/insserv": File o directory non esistente at /usr/sbin/update-rc.d line 382.
update-rc.d: error: insserv rejected the script header
and then

Code: [Select]

jls@box:~$ ps|grep conn
root     11269     1  4 18:22 ?        00:00:00 /usr/sbin/connmand
root     11289     1  0 18:22 ?        00:00:00 /usr/sbin/connman-vpnd -n
jls      11310 11171  0 18:22 pts/0    00:00:00 grep conn
I see the process has been started.
I have connman in base which is the first loaded sce during boot, here is it's lst:

Code: [Select]

alsa-utils
pulseaudio-module-x11
vim
dbus
wireless
libgtk2.0-0
grep
libxfont1
libmount1
dbus-x11
gtk2-engines-pixbuf
libcurl3
libdbus-glib-1-2
linux-firmware
kernel-all-3.16.6-tinycore
policykit-1
udisks2
Xprogs
connman
base-locale
language-pack-it
language-pack-gnome-it-base
ntpdate
xdg-utils
crda
how are the order of package loading inside an lst?
From first to last?
Maybe I should put connman on top or at the bottom? Actually it's already quite at the end of the list.
Thanks

[Jason W]

Order is from first to last.   But if there is any startup script action that is needed by a package that is called by one of it's deps and needs to be done before it, then we enter that action in the startup script that needs it.  I see the error too, I will look into it.

[Jason W]

If I enter the command "/etc/init.d/connman start" connman starts and does not produce any errors. 

[jls]

Yes but also the postinstall script correctly launches the daemon but this does not happen during boot

[Jason W]

Ok, I see.