All of lore.kernel.org
 help / color / mirror / Atom feed
* System service
@ 2019-05-02 14:55 JH
  2019-05-02 17:28 ` Timothy Froehlich
       [not found] ` <CALbNGRTR2u3Oq0bDi6W30zCcFo7dt+O3BMKrauhyhTPV8kQ8=g@mail.gmail.com>
  0 siblings, 2 replies; 6+ messages in thread
From: JH @ 2019-05-02 14:55 UTC (permalink / raw)
  To: Yocto discussion list

Hi,

The official ofono.inc recipe defines SYSTEMD_SERVICE_${PN} =
"ofono.service", but when I built the image, the system service does
not start ofono daemon automatically, I have to run the ofono daemon
manually. What I could be missing here? Here is the ofono recipes,
sorry if I need to ask ofono mailing list.

$ cat ofono.inc
HOMEPAGE = "http://www.ofono.org"
SUMMARY  = "open source telephony"
DESCRIPTION = "oFono is a stack for mobile telephony devices on Linux.
oFono supports speaking to telephony devices through specific drivers,
or with generic AT commands."
LICENSE  = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a \

file://src/ofono.h;beginline=1;endline=20;md5=3ce17d5978ef3445def265b98899c2ee"

inherit autotools pkgconfig update-rc.d systemd bluetooth
gobject-introspection-data

DEPENDS  = "dbus glib-2.0 udev mobile-broadband-provider-info"

INITSCRIPT_NAME = "ofono"
INITSCRIPT_PARAMS = "defaults 22"

PACKAGECONFIG ??= "\
    ${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)} \
    ${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez', '', d)} \
    "
PACKAGECONFIG[systemd] =
"--with-systemdunitdir=${systemd_unitdir}/system/,--with-systemdunitdir="
PACKAGECONFIG[bluez] = "--enable-bluetooth, --disable-bluetooth, ${BLUEZ}"

EXTRA_OECONF += "--enable-test"

SYSTEMD_SERVICE_${PN} = "ofono.service"

do_install_append() {
  install -d ${D}${sysconfdir}/init.d/
  install -m 0755 ${WORKDIR}/ofono ${D}${sysconfdir}/init.d/ofono
}

PACKAGES =+ "${PN}-tests"

RDEPENDS_${PN} += "dbus"
RRECOMMENDS_${PN} += "kernel-module-tun mobile-broadband-provider-info"

FILES_${PN} += "${systemd_unitdir}"
FILES_${PN}-tests = "${libdir}/${BPN}/test"
RDEPENDS_${PN}-tests = "python3 python3-dbus"
RDEPENDS_${PN}-tests += "${@bb.utils.contains('GI_DATA_ENABLED',
'True', 'python3-pygobject', '', d)}"

Thank you.

- jupiter


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: System service
  2019-05-02 14:55 System service JH
@ 2019-05-02 17:28 ` Timothy Froehlich
  2019-05-02 18:15   ` Henrik Lindblom
       [not found] ` <CALbNGRTR2u3Oq0bDi6W30zCcFo7dt+O3BMKrauhyhTPV8kQ8=g@mail.gmail.com>
  1 sibling, 1 reply; 6+ messages in thread
From: Timothy Froehlich @ 2019-05-02 17:28 UTC (permalink / raw)
  To: JH; +Cc: Yocto discussion list

[-- Attachment #1: Type: text/plain, Size: 3008 bytes --]

Looks like it's dropping the service in ${sysconfdir}/init.d which resolves
to /etc/init.d. I'm not sure that systemd won't look into init.d for
services. The standard place to put them is ${D}/${systemd_system_unitdir},
which resolves to /lib/systemd/system.

Also, check the "SYSTEMD_AUTO_ENABLE_pn-ofono" variable for that recipe.
The systemd class sets it to "enable" by default, but something else could
be overriding it and setting it to "disable".  Alternatively, confirm that
the service isn't actually starting up and failing. It may be that you're
restarting it once the system is fully booted and everything ofono needs is
now ready.

On Thu, May 2, 2019 at 7:55 AM JH <jupiter.hce@gmail.com> wrote:

> Hi,
>
> The official ofono.inc recipe defines SYSTEMD_SERVICE_${PN} =
> "ofono.service", but when I built the image, the system service does
> not start ofono daemon automatically, I have to run the ofono daemon
> manually. What I could be missing here? Here is the ofono recipes,
> sorry if I need to ask ofono mailing list.
>
> $ cat ofono.inc
> HOMEPAGE = "http://www.ofono.org"
> SUMMARY  = "open source telephony"
> DESCRIPTION = "oFono is a stack for mobile telephony devices on Linux.
> oFono supports speaking to telephony devices through specific drivers,
> or with generic AT commands."
> LICENSE  = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a \
>
>
> file://src/ofono.h;beginline=1;endline=20;md5=3ce17d5978ef3445def265b98899c2ee"
>
> inherit autotools pkgconfig update-rc.d systemd bluetooth
> gobject-introspection-data
>
> DEPENDS  = "dbus glib-2.0 udev mobile-broadband-provider-info"
>
> INITSCRIPT_NAME = "ofono"
> INITSCRIPT_PARAMS = "defaults 22"
>
> PACKAGECONFIG ??= "\
>     ${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)} \
>     ${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez', '', d)} \
>     "
> PACKAGECONFIG[systemd] =
> "--with-systemdunitdir=${systemd_unitdir}/system/,--with-systemdunitdir="
> PACKAGECONFIG[bluez] = "--enable-bluetooth, --disable-bluetooth, ${BLUEZ}"
>
> EXTRA_OECONF += "--enable-test"
>
> SYSTEMD_SERVICE_${PN} = "ofono.service"
>
> do_install_append() {
>   install -d ${D}${sysconfdir}/init.d/
>   install -m 0755 ${WORKDIR}/ofono ${D}${sysconfdir}/init.d/ofono
> }
>
> PACKAGES =+ "${PN}-tests"
>
> RDEPENDS_${PN} += "dbus"
> RRECOMMENDS_${PN} += "kernel-module-tun mobile-broadband-provider-info"
>
> FILES_${PN} += "${systemd_unitdir}"
> FILES_${PN}-tests = "${libdir}/${BPN}/test"
> RDEPENDS_${PN}-tests = "python3 python3-dbus"
> RDEPENDS_${PN}-tests += "${@bb.utils.contains('GI_DATA_ENABLED',
> 'True', 'python3-pygobject', '', d)}"
>
> Thank you.
>
> - jupiter
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


-- 
Tim Froehlich
Embedded Linux Engineer
tfroehlich@archsys.io
215-218-8955

[-- Attachment #2: Type: text/html, Size: 4232 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: System service
  2019-05-02 17:28 ` Timothy Froehlich
@ 2019-05-02 18:15   ` Henrik Lindblom
  2019-05-02 20:02     ` [EXTERNAL] " Lukasz Zemla
  0 siblings, 1 reply; 6+ messages in thread
From: Henrik Lindblom @ 2019-05-02 18:15 UTC (permalink / raw)
  To: Timothy Froehlich; +Cc: Yocto discussion list

[-- Attachment #1: Type: text/plain, Size: 4509 bytes --]

> Looks like it's dropping the service in ${sysconfdir}/init.d which
> resolves to /etc/init.d. I'm not sure that systemd won't look into
> init.d for services.

It doesn't.

> The standard place to put them is ${D}/${systemd_system_unitdir},
> which resolves to /lib/systemd/system.

Systemd's unit search path is documented in

https://www.freedesktop.org/software/systemd/man/systemd.unit.html

but the ones I've personally used most are /usr/lib/systemd/user and
/etc/systemd/system. These are a personal preference more than
anything else.

>> do_install_append() {
>>   install -d ${D}${sysconfdir}/init.d/
>>   install -m 0755 ${WORKDIR}/ofono ${D}${sysconfdir}/init.d/ofono
>> }

do_install() seems to be installing only non-systemd ofono shell
script in.

>> FILES_${PN} += "${systemd_unitdir}"

This line is redundant, AFAIK, since systemd.bbclass will handle
packaging for you, assuming you install the service files that you
advertise in SYSTEMD_SERVICE_${PN}. However, as I'm writing this from
memory, I recommend you skim through the class definition and check
for further details there.

Cheers,
Henrik

On Thu, May 2, 2019 at 8:28 PM Timothy Froehlich <tfroehlich@archsys.io>
wrote:

> Looks like it's dropping the service in ${sysconfdir}/init.d which
> resolves to /etc/init.d. I'm not sure that systemd won't look into init.d
> for services. The standard place to put them
> is ${D}/${systemd_system_unitdir}, which resolves to /lib/systemd/system.
>
> Also, check the "SYSTEMD_AUTO_ENABLE_pn-ofono" variable for that recipe.
> The systemd class sets it to "enable" by default, but something else could
> be overriding it and setting it to "disable".  Alternatively, confirm that
> the service isn't actually starting up and failing. It may be that you're
> restarting it once the system is fully booted and everything ofono needs is
> now ready.
>
> On Thu, May 2, 2019 at 7:55 AM JH <jupiter.hce@gmail.com> wrote:
>
>> Hi,
>>
>> The official ofono.inc recipe defines SYSTEMD_SERVICE_${PN} =
>> "ofono.service", but when I built the image, the system service does
>> not start ofono daemon automatically, I have to run the ofono daemon
>> manually. What I could be missing here? Here is the ofono recipes,
>> sorry if I need to ask ofono mailing list.
>>
>> $ cat ofono.inc
>> HOMEPAGE = "http://www.ofono.org"
>> SUMMARY  = "open source telephony"
>> DESCRIPTION = "oFono is a stack for mobile telephony devices on Linux.
>> oFono supports speaking to telephony devices through specific drivers,
>> or with generic AT commands."
>> LICENSE  = "GPLv2"
>> LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a \
>>
>>
>> file://src/ofono.h;beginline=1;endline=20;md5=3ce17d5978ef3445def265b98899c2ee"
>>
>> inherit autotools pkgconfig update-rc.d systemd bluetooth
>> gobject-introspection-data
>>
>> DEPENDS  = "dbus glib-2.0 udev mobile-broadband-provider-info"
>>
>> INITSCRIPT_NAME = "ofono"
>> INITSCRIPT_PARAMS = "defaults 22"
>>
>> PACKAGECONFIG ??= "\
>>     ${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)} \
>>     ${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez', '', d)}
>> \
>>     "
>> PACKAGECONFIG[systemd] =
>> "--with-systemdunitdir=${systemd_unitdir}/system/,--with-systemdunitdir="
>> PACKAGECONFIG[bluez] = "--enable-bluetooth, --disable-bluetooth, ${BLUEZ}"
>>
>> EXTRA_OECONF += "--enable-test"
>>
>> SYSTEMD_SERVICE_${PN} = "ofono.service"
>>
>> do_install_append() {
>>   install -d ${D}${sysconfdir}/init.d/
>>   install -m 0755 ${WORKDIR}/ofono ${D}${sysconfdir}/init.d/ofono
>> }
>>
>> PACKAGES =+ "${PN}-tests"
>>
>> RDEPENDS_${PN} += "dbus"
>> RRECOMMENDS_${PN} += "kernel-module-tun mobile-broadband-provider-info"
>>
>> FILES_${PN} += "${systemd_unitdir}"
>> FILES_${PN}-tests = "${libdir}/${BPN}/test"
>> RDEPENDS_${PN}-tests = "python3 python3-dbus"
>> RDEPENDS_${PN}-tests += "${@bb.utils.contains('GI_DATA_ENABLED',
>> 'True', 'python3-pygobject', '', d)}"
>>
>> Thank you.
>>
>> - jupiter
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
> --
> Tim Froehlich
> Embedded Linux Engineer
> tfroehlich@archsys.io
> 215-218-8955
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 6724 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [EXTERNAL] Re: System service
  2019-05-02 18:15   ` Henrik Lindblom
@ 2019-05-02 20:02     ` Lukasz Zemla
  0 siblings, 0 replies; 6+ messages in thread
From: Lukasz Zemla @ 2019-05-02 20:02 UTC (permalink / raw)
  To: Yocto discussion list

On Thursday, May 02, 2019 8:15 PM, Henrik Lindblom wrote:
>>> FILES_${PN} += "${systemd_unitdir}"
>
> This line is redundant, AFAIK, since systemd.bbclass will handle
> packaging for you, assuming you install the service files that you
> advertise in SYSTEMD_SERVICE_${PN}. However, as I'm writing this from
> memory, I recommend you skim through the class definition and check
> for further details there.

I confirm - this line is not required (at least at Yocto 2.6).

Best regards,
Lukasz Zemla

***
The information in this email is confidential and intended solely for the individual or entity to whom it is addressed.  If you have received this email in error please notify the sender by return e-mail, delete this email, and refrain from any disclosure or action based on the information.
***

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: System service
       [not found]   ` <CAA=hcWSFeokUgsN45HyKVQ=ky9Cp8bPCAvmwTM_SZ=FH2=6npA@mail.gmail.com>
@ 2019-05-03  8:28     ` Andreas Müller
  0 siblings, 0 replies; 6+ messages in thread
From: Andreas Müller @ 2019-05-03  8:28 UTC (permalink / raw)
  To: JH, Yocto Project

On Fri, May 3, 2019 at 10:22 AM JH <jupiter.hce@gmail.com> wrote:
>
> Hi Andreas,
>
> > In cases like these:
> >
> > * expecting sytemd starting service automatically
> > * something went wrong
> >
> > I ask systemd for it with 'systemctl status <service>'
> >
> > So what does 'systemctl status ofono' say?
>
> You right, it was aborted, but it had no problems to be started
> manually, a little mysterious, need further investigation. Thanks
> Andreas.
>
> # systemctl status ofono
> ��● ofono.service - Telephony service
>    Loaded: loaded
> (8;;file://solarevk/lib/systemd/system/ofono.service/lib/systemd/system/ofono.service8;;;
> enabled; vendor preset: enabled)
>    Active: failed (Result: exit-code) since Fri 2019-05-03 01:01:04 UTC; 7h ago
>   Process: 218 ExecStart=/usr/sbin/ofonod -n (code=exited, status=1/FAILURE)
>  Main PID: 218 (code=exited, status=1/FAILURE)
>
> May 03 01:01:01 solarevk systemd[1]: Starting Telephony service...
> May 03 01:01:01 solarevk ofonod[218]: oFono version 1.24
> May 03 01:01:01 solarevk systemd[1]: Started Telephony service.
> May 03 01:01:03 solarevk ofonod[218]: Aborting (signal 11) [/usr/sbin/ofonod]
> May 03 01:01:04 solarevk systemd[1]: ofono.service: Main process
> exited, co��…LURE
> May 03 01:01:04 solarevk systemd[1]: ofono.service: Failed with result
> 'exi��…de'.
> Hint: Some lines were ellipsized, use -l to show in full.
>
> # systemctl status ofono
> ��● ofono.service - Telephony service
>    Loaded: loaded (8;;file://solarevk/lib/systemd/system/ofono.service/lib/syst)
>    Active: active (running) since Fri 2019-05-03 08:18:59 UTC; 2s ago
>  Main PID: 275 (ofonod)
>    CGroup: /system.slice/ofono.service
>            ��└��─275 /usr/sbin/ofonod -n
>
> May 03 08:18:59 solarevk systemd[1]: Starting Telephony service...
> May 03 08:18:59 solarevk ofonod[275]: oFono version 1.24
> May 03 08:18:59 solarevk systemd[1]: Started Telephony service.
> May 03 08:19:00 solarevk ofonod[275]: Interface org.ofono.AllowedAccessPoin��…lt
> Hint: Some lines were ellipsized, use -l to show in full.

Accidentally I made this a private discussion - make it public again
so others with similar issues might not need to ask again :)

Andreas


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: System service
@ 2019-05-02 20:08 Lukasz Zemla
  0 siblings, 0 replies; 6+ messages in thread
From: Lukasz Zemla @ 2019-05-02 20:08 UTC (permalink / raw)
  To: Yocto discussion list

On Thursday, May 02, 2019 8:15 PM, Henrik Lindblom wrote:
>>> FILES_${PN} += "${systemd_unitdir}"
>
> This line is redundant, AFAIK, since systemd.bbclass will handle 
> packaging for you, assuming you install the service files that you 
> advertise in SYSTEMD_SERVICE_${PN}. However, as I'm writing this from 
> memory, I recommend you skim through the class definition and check 
> for further details there.

I confirm - this line is not required (at least at Yocto 2.6).

Best regards,
Lukasz Zemla

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-05-03  8:29 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-02 14:55 System service JH
2019-05-02 17:28 ` Timothy Froehlich
2019-05-02 18:15   ` Henrik Lindblom
2019-05-02 20:02     ` [EXTERNAL] " Lukasz Zemla
     [not found] ` <CALbNGRTR2u3Oq0bDi6W30zCcFo7dt+O3BMKrauhyhTPV8kQ8=g@mail.gmail.com>
     [not found]   ` <CAA=hcWSFeokUgsN45HyKVQ=ky9Cp8bPCAvmwTM_SZ=FH2=6npA@mail.gmail.com>
2019-05-03  8:28     ` Andreas Müller
2019-05-02 20:08 Lukasz Zemla

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.