3900 2013-02-18 12:10:57 +0000 systemd fails to start .sh init scripts 2013-05-13 15:04:43 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.4 x86 Multiple RESOLVED FIXED Medium normal 1.4.1 1 ross.burton radu.moisan holger meta.mr.watcher meta.watcher Qi.Chen radu.moisan ross.burton sgw --- --- --- oldest_to_newest 29912 0 ross.burton 2013-02-18 12:10:57 +0000 From Holger on the oe-core list: > I am using the busybox ifplugd to > configure the network on plug/un-plug of the cable. My start script ended > with .sh in the name. systemd recognized the script but failed to start > it. Renaming it to not end with .sh fixed the issue for me. This is more > like a systemd bug than OE but I wonder if we could change update-rc.d > bbclass to check the for the .sh in the start script and then complain > about it? 29939 1 Qi.Chen 2013-02-19 03:02:12 +0000 There's a similar bug in sysvinit in our system. https://bugzilla.yoctoproject.org/show_bug.cgi?id=3612 33065 2 radu.moisan 2013-05-13 10:44:50 +0000 this is not an issue anymore. I acknowledge the behavior in past, but now with lastest master (f7afeeb75993b159bb8959e0309bc5eb3978a8fb) all *.sh scripts seem to work. Tried to enable manually banner.sh and it works. Also rmnologin.sh works, as the service is alive and no warnings found in logs. Tried psplash.sh as well, and the service is started. 33068 3 ross.burton 2013-05-13 15:04:43 +0000 Confirmed, this piece of code that is now enabled always and not just for some distros is the fix: if (endswith(name, ".sh")) /* Drop .sh suffix */ strcpy(stpcpy(r, name) - 3, ".service");