(2015-11-24, 01:04)Karnis Wrote: I rolled back to 1119 but the post-reboot-OE message saying "waiting for network" for about 2 seconds issue persisted. Again, my network connection is unaffected.
Yes, it's coming from the
network-online.service.
In a worst case you may see the following, which isn't very nice, though not a show-stopper (I only ever reboot when updating, as I'm able to suspend/resume reliably).
It started with
#1121 (which bumped systemd), and the reason it's also there in #1119 is because #1121 is adding a whole bunch of new persistent system.d services in /storage/.config/system.d:
/storage/.config/system.d in build #1119 (before booting #1121):
Code:
OpenELEC (unofficial) Version: devel-20151119035205-#1119-g785752e
OpenELEC git: 785752e5df9c5cf284e915d5916ebe30c290d515
OpenELEC:~ # ls -la /storage/.config/system.d
total 40
32 -rw-r--r-- 1 root root 28816 Nov 28 04:03 README
4 -rw-r--r-- 1 root root 1772 Nov 28 04:03 cifs.mount.sample
4 -rw-r--r-- 1 root root 1729 Nov 28 04:03 nfs.mount.sample
/storage/.config/system.d in build #1121:
Code:
OpenELEC (unofficial) Version: devel-20151121220629-#1121-g297af74
OpenELEC git: 297af74bdf741f12076a4a503dd1acf1baa57399
OpenELEC:~ # ls -la /storage/.config/system.d
total 108
drwxr-xr-x 17 root root 4096 Nov 28 04:07 .
drwxr-xr-x 17 root root 4096 Nov 28 04:03 ..
-rw-r--r-- 1 root root 28816 Nov 28 04:03 README
drwxr-xr-x 2 root root 4096 Nov 28 04:07 basic.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 bluetooth.target.wants
-rw-r--r-- 1 root root 1772 Nov 28 04:03 cifs.mount.sample
lrwxrwxrwx 1 root root 37 Nov 28 04:07 ctrl-alt-del.target -> /usr/lib/systemd/system/reboot.target
lrwxrwxrwx 1 root root 46 Nov 28 04:07 dbus-fi.epitest.hostap.WPASupplicant.service -> /usr/lib/systemd/system/wpa_supplicant.service
lrwxrwxrwx 1 root root 35 Nov 28 04:07 default.target -> /usr/lib/systemd/system/kodi.target
drwxr-xr-x 2 root root 4096 Nov 28 04:07 graphical.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 halt.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 installer.target.wants
lrwxrwxrwx 1 root root 37 Nov 28 04:07 kbrequest.target -> /usr/lib/systemd/system/rescue.target
drwxr-xr-x 2 root root 4096 Nov 28 04:07 kodi.service.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 kodi.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 local-fs.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 multi-user.target.wants
-rw-r--r-- 1 root root 1729 Nov 28 04:03 nfs.mount.sample
drwxr-xr-x 2 root root 4096 Nov 28 04:07 poweroff.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 reboot.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 sleep.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 sockets.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 sysinit.target.wants
drwxr-xr-x 2 root root 4096 Nov 28 04:07 textmode.target.wants
Consequently, rolling back to #1119 (or *any* systemd-based OE release) from #1121 means you still have all these extra system.d services starting, which appears to delay start up long enough for the "waiting on Network to come online ..." mesage to appear.
I'll raise it as an issue on OpenELEC github.
Edit: Issue
#4470 on OpenELEC github. Wonder if this might also be responsible for the WiFi issues, as it would explain why the WiFi issues continue after rolling back to a version prior to #1121.
