Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: # honister #systemd attempting to run script on boot...
Date: Tue, 11 Oct 2022 19:54:53 +0000	[thread overview]
Message-ID: <20221011195503.3A33EC433F5@smtp.lore.kernel.org> (raw)

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


I am trying to make use of system to run a test script at boot...
I can exercise my test_script/test_script.service manually using systemctl commands and it appears to work as expects.

I created a recipe based on this, it builds clean (no errors/warnings), but it doesn't appear to set things up correctly.
I have only recently begun working with honister, and new to systemd...

Could someone have look at my recipe & service file and see if they can spot anything ?

My recipe:

#
# This file is the my_test_script recipe.
#

SUMMARY = "Simple my_test_script application"
SECTION = "apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

inherit systemd

SRC_URI = "file://test_script.sh \
           file://test_script.service"

S = "${WORKDIR}"

SYSTEMD_PACKAGES = "${PN}"
SYSTEMD_SERVICE_${PN} = "test_script.service"
SYSTEMD_AUTO_ENABLE:${PN} = "enable"

do_install() {
             install -d ${D}${bindir}
             install -m 0755 ${S}/test_script.sh ${D}${bindir}

             install -d ${D}${systemd_system_unitdir}
             install -m 0644 ${S}/test_script.service ${D}${systemd_system_unitdir}
}

FILES_${PN} = "${bindir}"
FILES_${PN} += "${systemd_system_unitdir}"

REQUIRED_DISTRO_FEATURES="systemd"
---
My test script service file:

[Unit]
Description=Configure test

[Service]
Type=oneshot
ExecStart=/usr/bin/test_script.sh start
StandardOutput=journal+console

[Install]
WantedBy=multi-user.target
---
My test script:

#!/bin/bash
# description: Description comes here....

echo "*******************************"
echo "START: Hello PetaLinux World :)"
date +"%m/%d/%Y %H:%M:%S $HOSTNAME"
echo "*******************************"

Thanks,
Steve

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

             reply	other threads:[~2022-10-11 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 19:54 Monsees, Steven C (US) [this message]
     [not found] <MADEUP.171D1BE272B653C5.8969@lists.yoctoproject.org>
2022-10-12 18:28 ` # honister #systemd attempting to run script on boot Monsees, Steven C (US)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221011195503.3A33EC433F5@smtp.lore.kernel.org \
    --to=steven.monsees@baesystems.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox