From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] systemd: add option to enable systemd-journal-remote
Date: Thu, 28 Nov 2019 09:27:57 +0100 [thread overview]
Message-ID: <20191128092757.19886364@windsurf> (raw)
In-Reply-To: <CAFvCimXHMv94tg4S-U5QLu4k26HZAtZXsVR3jjK2C4s+XOuX2g@mail.gmail.com>
Hello,
On Thu, 28 Nov 2019 09:08:19 +0100
J?r?my ROSEN <jeremy.rosen@smile.fr> wrote:
> Ok, as usuall some background knowledge
>
> systemd provides three binaries to deal with sending journal data over the
> network
>
> * systemd-journald-gateway : a tiny HTTP server that provides the logs
> * systemd-journald-upload : a process to run periodically to push the logs
> to a remote HTTP server
> * systemd-journald-remote : aprocess to run on the remorse computer (not on
> the target) to receive data and/or to fetch data from the target
>
> All three options are selected together with -Dremote=true (which is the
> default). It would be nice to be able to select them individually, but
> upstream does not provide that option.
>
> gatewayd is a bit more tricky because it will detect if libmicrohttpd is
> available and only builds if it is.
>
> So, as a fix I would make BR2_PACKAGE_SYSTEMD_JOURNAL_GATEWAY depend
> on BR2_PACKAGE_SYSTEMD_JOURNAL_REMOTE
> Also, fix default values to match previous behaviour
But if all of gateway, upload and remote are always built together when
-Dremote=true, what is the point of having fine-grained options for
each of gateway, upload and remote ? Just to install/enable (or not)
the correspond service file ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-28 8:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 3:05 [Buildroot] [PATCH] systemd: add option to enable systemd-journal-remote Yi Zheng
2019-06-13 15:35 ` Yann E. MORIN
2019-06-17 19:40 ` Thomas Petazzoni
2019-06-18 7:05 ` Yi Zheng
2019-11-27 20:46 ` Thomas Petazzoni
2019-11-28 8:08 ` Jérémy ROSEN
2019-11-28 8:27 ` Thomas Petazzoni [this message]
2019-11-28 15:15 ` Jérémy ROSEN
2019-11-28 9:33 ` Yi Zheng
2020-10-13 15:16 ` Michael Nosthoff
2020-10-13 15:35 ` Thomas Petazzoni
2020-10-13 15:40 ` Michael Nosthoff
2020-10-13 15:49 ` Thomas Petazzoni
2020-10-13 16:28 ` Yann E. MORIN
2020-10-13 17:03 ` Yann E. MORIN
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=20191128092757.19886364@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 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.