[systemd-devel] Weston not launching Via Service file.

Hello, We are working on Genivi14, in which we are trying to launch weston via service file. It is not working if iam giving Type=notify in service file. my build configuration is as follows: Build Configuration: BB_VERSION = "1.36.0" BUILD_SYS= "x86_64-linux"

Re: [systemd-devel] [PATCH 0/6] pstore: Tool to archive contents of pstore upon boot/shutdown

OK, will do! eric On 5/16/19 9:34 AM, Lennart Poettering wrote: On Do, 16.05.19 09:28, Eric DeVolder (eric.devol...@oracle.com) wrote: Could you please submit this via github as PR? Review is so much nicer there, in particular for complex patch sets, and this qualifies as complex I think. This

Re: [systemd-devel] interacting with logind to detect user idle time

To do practise I am using NetworkManager example [1] All macros passed as arguments to functions g_dbus_proxy_call_sync g_dbus_proxy_new_for_bus_sync are implemented at [2]. Is there an equivalent of [2] for logind? I made a quick search into systemd repository [3] but I am getting too many

Re: [systemd-devel] [PATCH 6/6] pstore: The new documentation for the pstore configuration file

Patchset imported to github. To create a pull request, one of the main developers has to initiate one via: -- Generated by https://github.com/haraldh/mail2git

Re: [systemd-devel] Schedule reboot in *.service file

On Thu, May 16, 2019 at 4:50 AM Lennart Poettering wrote: > > On Mi, 15.05.19 15:53, Jeffrey Walton (noloa...@gmail.com) wrote: > > > if [[ "$NEEDS_REBOOT" -eq 1 ]] > > then > > echo "Scheduling reboot in 10 minutes" > > reboot -r 10 > > This syntax is not understood by systemd: > >

Re: [systemd-devel] [PATCH 0/6] pstore: Tool to archive contents of pstore upon boot/shutdown

On Do, 16.05.19 09:28, Eric DeVolder (eric.devol...@oracle.com) wrote: Could you please submit this via github as PR? Review is so much nicer there, in particular for complex patch sets, and this qualifies as complex I think. This also has the benefit that the code is automatically analyzed by

[systemd-devel] [PATCH 0/6] pstore: Tool to archive contents of pstore upon boot/shutdown

This patch introduces the systemd pstore service which will archive the contents of the Linux persistent storage filesystem, pstore, to other storage, thus preserving the existing information contained in the pstore, and clearing pstore storage for future error events. Linux provides a persistent

[systemd-devel] [PATCH 4/6] pstore: The new configuration file for systemd-pstore tool

The pstore.conf configuration file has four settings, described below. - Storage : one of "none", "archive", or "journal". With "none", this tool leaves the contents of pstore untouched. With "archive", the contents of the pstore are moved into the ArchiveDir. With "journal", the

[systemd-devel] [PATCH 3/6] pstore: The new systemd-pstore tool to archive pstore contents

The systemd-pstore which is a tool that performs the following: - reads the pstore.conf configuration file - lists the files in the pstore (eg. /sys/fs/pstore) - for each file, locates a handler for the type of file (eg. dmesg, MCE, etc) - invokes the handler for the file (eg. the handler

[systemd-devel] [PATCH 2/6] pstore: Add new pstore tool/service to the build

This new file is invoked by the build system to build pstore. Signed-off-by: Eric DeVolder --- src/pstore/meson.build | 21 + 1 file changed, 21 insertions(+) create mode 100644 src/pstore/meson.build diff --git a/src/pstore/meson.build b/src/pstore/meson.build new file

[systemd-devel] [PATCH 6/6] pstore: The new documentation for the pstore configuration file

The xml file for the systemd pstore tool configuration file. Signed-off-by: Eric DeVolder --- man/pstore.conf.xml | 100 1 file changed, 100 insertions(+) create mode 100644 man/pstore.conf.xml diff --git a/man/pstore.conf.xml

[systemd-devel] [PATCH 5/6] pstore: The new pstore archive service file

The necessary systemd service file which invokes the pstore archival tool upon boot as well as shutdown (poweroff, reboot). Signed-off-by: Eric DeVolder --- units/systemd-pstore.service.in | 32 1 file changed, 32 insertions(+) create mode 100644

[systemd-devel] [PATCH 1/6] pstore: Add new pstore tool/service to the build

This change adds the src/pstore directory to the build files. Signed-off-by: Eric DeVolder --- meson.build | 29 + meson_options.txt | 2 ++ units/meson.build | 1 + 3 files changed, 32 insertions(+) diff --git a/meson.build b/meson.build index

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

On Do, 16.05.19 12:04, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > > This is explained in the documentation btw: > > https://www.freedesktop.org/software/systemd/man/systemd.generator.html > > > > Long story short: it's about unit file precedence. > > Sorry I don't get it: So the

Re: [systemd-devel] Antw: Re: Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

Am 16.05.19 um 12:41 schrieb Ulrich Windl: >> Please, this is just wasting everyone's time. Take the advice that >> Reindl gave you: generators are an advanced tool that you don't need >> when staring with systemd. > > Yes systemd is for you developers, not for developers like me. Your're the >

[systemd-devel] Antw: Re: Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

>>> Zbigniew Jedrzejewski-Szmek schrieb am 16.05.2019 um 12:13 in Nachricht <20190516101348.gn9...@in.waw.pl>: > On Thu, May 16, 2019 at 12:04:28PM +0200, Ulrich Windl wrote: >> >>> Lennart Poettering schrieb am 16.05.2019 um 10:29 >> in >> Nachricht <20190516082910.GA24042@gardel-login>: >> >

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

On Thu, May 16, 2019 at 12:04:28PM +0200, Ulrich Windl wrote: > >>> Lennart Poettering schrieb am 16.05.2019 um 10:29 > in > Nachricht <20190516082910.GA24042@gardel-login>: > > On Do, 16.05.19 08:55, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) > wrote: > > > >> Hi! > >> > >> After having

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

>>> Lennart Poettering schrieb am 16.05.2019 um 10:29 in Nachricht <20190516082910.GA24042@gardel-login>: > On Do, 16.05.19 08:55, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> After having read the page again, it's not more clear than >> before. Even I have some more

Re: [systemd-devel] Stop systemd timer upon success script and restart the next day

On Mi, 15.05.19 16:21, Jeffrey Walton (noloa...@gmail.com) wrote: > I have a systemd timer that starts a service, and the service executes > a script that downloads data files once a day. Once the data files are > retrieved I don't need the timer for the remainder of the day. > However, I need

Re: [systemd-devel] Schedule reboot in *.service file

On Mi, 15.05.19 15:53, Jeffrey Walton (noloa...@gmail.com) wrote: > if [[ "$NEEDS_REBOOT" -eq 1 ]] > then > echo "Scheduling reboot in 10 minutes" > reboot -r 10 This syntax is not understood by systemd: https://www.freedesktop.org/software/systemd/man/reboot.html# If you want to

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

On Do, 16.05.19 08:55, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > Hi! > > After having read the page again, it's not more clear than > before. Even I have some more questions: > > Why do generators receive three directory paths: Should the > generator decide where at those three

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

Hi! After having read the page again, it's not more clear than before. Even I have some more questions: Why do generators receive three directory paths: Should the generator decide where at those three paths to add a unit? How should it know? Wouldn't it be easier to provide one path and