Hi Grant, On Wed, 28 Mar 2012 12:26:20 -0700 Grant Erickson <[email protected]> wrote:
> On 3/28/12 11:35 AM, Mario Domenech Goulart wrote: >> I've been facing a weird behavior on the system I'm working. I'll >> try to describe it here. >> >> I'm using a regular PC with an ethernet card (eth0), ConnMan 0.79 >> under Linux (3.2.7). ConnMan is started by systemd. Here are the steps >> to illustrate the problem: >> >> 1. Right after installed, the system boots and the network interface >> gets IP configuration via DHCP, as expected. >> >> 2. I set the network interface configuration as static and it works as >> expected. >> >> 3. I set the network interface configuration to be obtained via DHCP. >> It is configured via DHCP as expected. >> >> 4. I reboot the system. >> >> 5. The network interface is not configured. >> >> After performing those steps, I cannot make the network interface >> obtain its configuration via DHCP on system boot anymore. > > Mario: > > How is your system terminating connman? > > On normal termination, connman will write out the contents of > /var/lib/connman/default.profile (among other data). This, of course, > doesn't always happen instantaneously. If your system is not set up to > actually wait for connman to completely finish before shutting down or if it > resorts to killing connman when it doesn't shutdown in time, you could end > up with a corrupted, empty or incomplete default.profile. Thanks. That's a valuable tip. I'm using systemd. According to http://www.freedesktop.org/software/systemd/man/systemd.service.html it seems that systemd sends a SIGTERM by default and a SIGKILL, after a timeout, in case processes survive SIGTERM. What is the proper way to shut ConnMan down? Best wishes. Mario -- http://parenteses.org/mario _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
