Hi Jukka, On Thu, 29 Mar 2012 17:05:52 +0300 Jukka Rissanen <[email protected]> wrote:
> On 03/28/2012 09:35 PM, Mario Domenech Goulart wrote: >> Hi, >> >> 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: > > Have you tried to run connmand without systemd? > The systemd + connmand combination is probably not tested very > extensively so you should probably check if everything works ok if > systemd is ruled out from the setup. Just tried running connmand out of systemd. It doesn't seem to make any difference. I noticed that if I: 1. stop connmand (with SIGTERM)* 2. remove /var/lib/connman 3. start connmand The network interface gets its configuration via DHCP and works fine. I can stop/start connmand and the network interface keeps configured. However, if I set static IP configuration, then set DHCP again, the network interface won't get any configuration next time connmand is restarted. [*] After killing connmand with SIGTERM I can see that the last log lines are (after quite a lot of messages): src/dbus.c: __connman_dbus_cleanup() Exit So, I suspect it's handling the signal and being correctly terminated. Is it possible that something in /var/lib/connman is getting corrupted when I set the network interface to use static configuration? After I set static configuration, I checked with ifconfig if the configuration was correctly applied (it was). I used an IP number different from the one obtained via DHCP, so I could see it was actually changed. Is anybody able to reproduce this behavior? Best wishes. Mario -- http://parenteses.org/mario _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
