poky.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: jcmalek@lakeheadu.ca
To: poky@lists.yoctoproject.org
Subject: Re: stdout overwriting logger output for service units
Date: Tue, 06 Dec 2022 12:38:30 -0800	[thread overview]
Message-ID: <5232.1670359110085721504@lists.yoctoproject.org> (raw)
In-Reply-To: <CAMKF1sozCP6bcFdtQzPFugatp4wmrO8pS+_Kv+OAWiBX0OQq8Q@mail.gmail.com>

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

Thanks but no luck when I tried:

[Service]
StandardError=journal
StandardOutput=journal

Or:

[Service]
StandardError=kmsg
StandardOutput=kmsg

I still have the same problem in both of these cases.

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

      reply	other threads:[~2022-12-06 20:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 17:08 stdout overwriting logger output for service units jcmalek
2022-11-30  2:01 ` [poky] " Khem Raj
2022-12-06 20:38   ` jcmalek [this message]

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=5232.1670359110085721504@lists.yoctoproject.org \
    --to=jcmalek@lakeheadu.ca \
    --cc=poky@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).