Explore the possibility of making systemd-journald a templated service #12123
Labels
downstream/rhel
Tracking bugs for RHEL
journal
RFE 🎁
Request for Enhancement, i.e. a feature request
Comments
lnykryn
added
RFE 🎁
poettering
added a commit
to poettering/systemd
that referenced
this issue
Nov 28, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Nov 28, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Nov 28, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 2, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 4, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 4, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 9, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 13, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 17, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 19, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 20, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Dec 23, 2019
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 6, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 8, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 9, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 13, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 16, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 20, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 21, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 23, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 26, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 28, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
poettering
added a commit
to poettering/systemd
that referenced
this issue
Jan 28, 2020
If we do, we operate on a separate set of logs and runtime objects The namespace is configured via argv[1]. Fixes: systemd#12123 Fixes: systemd#10230 systemd#9519 (These latter two issues ask for slightly different stuff, but the usecases generally can be solved by running separate instances of journald now, hence also declaring that as "Fixes:")
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now if you want to log for a specific service to a separate log, have different retention,... it is not possible.
It should be relatively easy to make possible to start multiple journal daemons and for specific service create a new mount namespace that would redirect /dev/log & stuff to the different instance.
The text was updated successfully, but these errors were encountered: