Re: [systemd-devel] systemd219 and Realtime priority

trying to work out what I was doing wrong before I managed to find the information about those options not being applicable anymore Thanks Jon On Fri, 8 Nov 2019 at 10:24, Lukas Nykryn wrote: > Hi! > > I think you should contact the Red Hat support with this question. Most of > the

[systemd-devel] systemd219 and Realtime priority

through configuration? Thanks Jon ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] systemd user sessions?

I'd like a systemd unit (and only that unit) to be controlled by a specific user. The unit runs as this user, so I thought about user instances of systemd. This service should be started when the system starts, so you'd have to enable linger in systemd-logind for that to work. The question is how

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

and what may be", it is not real time so it is just a complete description of what is now and a description of what will be later... I can place an entry in fstab while I mkfs on the disk referenced, I often do - I maintain that this is not wrong - it is not mounted !, just not present yet.

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

On Mon, 2015-06-29 at 22:16 +0200, Reindl Harald wrote: > > Am 29.06.2015 um 21:36 schrieb jon: > > On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote: > >> On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote: > >> > >>> Reversing the logi

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote: > On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote: > > > Reversing the logic by adding a "mustexist" fstab option and keeping the > > default behaviour would fix it. > > At this time, system

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

On Mon, 2015-06-29 at 20:40 +0200, Lennart Poettering wrote: > On Mon, 29.06.15 18:50, jon (j...@jonshouse.co.uk) wrote: > > > > and why don't you just add "nofail" > > > it's way shorter then write a ton of emails > > > > Yes, this I

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

... be more radical, brings up networking/sshd with an admin console (if sshd is configured, as it often is) in parallel with local admin console Thanks, Jon ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

behaviour would fix it. Bringing up networking/sshd in parallel to the admin shell would also mitigate my issue I can see that both proposed solutions have issues, but I suspect I am not the only one who will not be pleased about this behavi

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

that the presence of a given FS is expected and > > failure to mount should crash out to admin, the install tools should > > then have been modified to add this option to fstab rather than changing > > the default behaviour. > > nonsense, the "nofail" was *not* invent

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

On Mon, 2015-06-29 at 17:54 +0200, Reindl Harald wrote: > Am 29.06.2015 um 17:01 schrieb jon: > > On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote: > >> > >> On 06/29/2015 02:08 PM, jon wrote: > >>> https://www.debian.org/releases/stable/amd

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote: > > On 06/29/2015 02:08 PM, jon wrote: > > https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system > > > > I just installed debian 8.1, on the wh

[systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system I just installed debian 8.1, on the whole my reaction is mixed, one thing however really pisses me off more than any other "5.6.1. Stricter handling of failing mounts during boot

Re: [systemd-devel] 'is-enabled' supported for legacy sysvinit scripts?

måndagen den 13 april 2015 07:26:14 skrev Nusenu: > Hi Andrei, > > thanks for your reply. > > > systemctl should still support it if your system supports chkconfig > > to manage initscripts. > > chkconfig was indeed not installed, but even after installing it, the > > is-enabled command output

[systemd-devel] Shell expressions in EnvironmentFile

Since EnvironmentFile in a service isn't sourced by any shell, shell expressions in it will obviously not work the way that they did in a SysV style script. Nor does it seems that the environment gets preserved between ExecStartPre (where one could run a script that sets environment variables to b

Re: [systemd-devel] proper way to shutdown/reboot host with systemd

On Tue, Aug 26, 2014 at 3:11 PM, Vasiliy Tolstov wrote: > What problem to run sync before that? I'm not understand. Also i can > run firfreeze ioctl to fs and run reboot. To get dirty data writed to > disk. Problem is that none of the shutdown logic of any init system (be it systemd, upstart, sys

Re: [systemd-devel] right way to log to rsyslog/syslog only?

On Thu, Aug 7, 2014 at 2:06 PM, Frantisek Hanzlik wrote: > It's good that I have no /var/log/journal/* files, but > - journald is still runnig (this isn't too imporatant, but when it >is possible work without it, it will be better) Why do you want this? As Johann very tersely replied, it's no

Re: [systemd-devel] [PATCH 2/2] units: add RequiresMountsFor=/usr/… to various systemd service files

etup. I'm well aware that a separate /usr not mounted in the initrd is an unsupported setup, but a separate /usr/local *is* supposed to work, and making a separate /usr slightly less broken when it comes at virtually no extra cost (on top of getti

Re: [systemd-devel] [PATCH 1/2] core: do not add default dependencies to /usr mount unit

At Tuesday 22 July 2014 04:46:31 Andrey Borzenkov wrote: > But what exact problem does it solve? Units thinking they can read from /usr before local-fs-pre.target ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop

[systemd-devel] [PATCH 2/2] units: add RequiresMountsFor=/usr/… to various systemd service files

Unless both /usr and /usr/local is mounted in the initrd these services might miss some of their configuration otherwise. --- units/systemd-binfmt.service.in | 1 + units/systemd-modules-load.service.in | 1 + units/systemd-sysctl.service.in | 1 + units/systemd-sysusers.service.

[systemd-devel] [PATCH 1/2] core: do not add default dependencies to /usr mount unit

This makes no difference if /usr was mounted in the initrd, and brings the behaviour of legacy systems closer to those with a propper initrd. --- src/core/mount.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/core/mount.c b/src/core/mount.c index 102bbef..39a9aaf 100644

[systemd-devel] [PATCH] core: collapse JOB_RELOAD on an inactive unit into JOB_NOP [v2]

The old behavior is inconsistent and confusing, this commit simplifies matters significantly: Before this commit: * systemctl try-restart on any inactive unit returns *success* immediately * systemctl reload on an inactive unit without a queued start job returns *failure* immediately * sys

Re: [systemd-devel] [PATCH 05/10] rules: skip 99-systemd.rules when not running systemd as init

onsdagen den 16 juli 2014 16:49:55 skrev Lennart Poettering: > On Wed, 16.07.14 12:09, Jon Severinsson (j...@severinsson.net) wrote: > > From: Tollef Fog Heen > > If you really want to support systems without systemd installed, then I'd > recommend placing this rules file

Re: [systemd-devel] [PATCH 09/10] kmod-static-nodes: condition execution on kmod binary

onsdagen den 16 juli 2014 16:52:57 skrev Lennart Poettering: > This appears unnecessary. The unit is conditionalized anyway on > CAP_SYS_MODULE, which is something a container should never ever have. OK, then I would like to nominate "e0c7469 units: conditionalize static device node logic on CAP

Re: [systemd-devel] [PATCH] sysv-generator: do not generate 'Wants' symlinks to generated service files that will be shadowed by a native unit.

At Wednesday 16 July 2014 17:17:40 Lennart Poettering wrote: > I am a bit concerned about this, as we will never be able to find all > the units that PID 1 will find, for example because generated units are > not included in the client's search paths... Right, but those cases have never been a pro

Re: [systemd-devel] Misc patches from the Debian systemd package

At Wednesday 16 July 2014 15:14:59 Jóhann B. Guðmundsson wrote: > It should not come as a surprise to anyone given that Debian has such an > diverse user base that there exist mass hacks in the distribution to > please them all so filtering is needed/expected before things are being > submitted ups

Re: [systemd-devel] [PATCH 07/10] units: order remote-fs.target after local-fs.target

lly be able to assume that if they request all remote file systems to be mounted, local file systems will be too. Also I would have a hard time explaining why a change of a remote mount to a local one should be allowed to cause regressions... / Jon ___

Re: [systemd-devel] [PATCH 08/10] units: make it possible to disable tmp.mount using systemctl

> tmp.mount is part of our default expected setup and should behave like > this by default without any presets or configuration. Which is why I made `make install` enable it, which wasn't in the original patch for Debian. > It can be overridden by an entry in fstab just fine. Why is that needed?

Re: [systemd-devel] [PATCH 06/10] tmpfiles: fix permissions of /run/lock and /run/lock/lockdev

onsdagen den 16 juli 2014 12:15:09 skrev du: > Why do you think this should be changed? Mostly because this is the way it has always been done in Debian, and changing it breaks some existing init scripts, but I'm ok with continuing to carry it as a Debian specific patch if it is not considered app

Re: [systemd-devel] [PATCH] sysv-generator: do not generate 'Wants' symlinks to generated service files that will be shadowed by a native unit.

onsdagen den 16 juli 2014 12:48:23 skrev du: > On Wed, Jul 16, 2014 at 11:57 AM, Jon Severinsson > wrote: > > +/* Do not generate 'Wants' symlinks to the generated service file > > if it > > + * will be shadowed by an existing nativ

[systemd-devel] [PATCH 04/10] rules: set default polling interval on removable devices as well

From: Martin Pitt The events_dfl_poll_msecs rule will not trigger if "block" is not a module, but built in. This will avoid udisks etc. having to poll from userspace, and provide proper ejection when the hardware eject button is pressed. Bug-Debian: https://bugs.debian.org/713877 Bug-Ubuntu: htt

[systemd-devel] [PATCH 10/10] shared: include stdbool.h in mkdir.h

From: Sjoerd Simons --- src/shared/mkdir.h | 1 + 1 file changed, 1 insertion(+) diff --git a/src/shared/mkdir.h b/src/shared/mkdir.h index d15ede6..dd5b41e 100644 --- a/src/shared/mkdir.h +++ b/src/shared/mkdir.h @@ -22,6 +22,7 @@ along with systemd; If not, see

[systemd-devel] [PATCH 08/10] units: make it possible to disable tmp.mount using systemctl

From: Michael Stapelberg But enable it by default in make install and systemd preset. --- Makefile.am | 4 ++-- system-preset/90-systemd.preset | 1 + units/tmp.mount | 3 +++ 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/Makefile.am b/Makefil

[systemd-devel] [PATCH 01/10] build-sys: don't move libgudev to /lib

From: Michael Biebl It depends on libgobject and libgmodule which are installed in /usr/lib. --- Makefile.am | 10 -- 1 file changed, 10 deletions(-) diff --git a/Makefile.am b/Makefile.am index a492a1f..94cd402 100644 --- a/Makefile.am +++ b/Makefile.am @@ -3373,16 +3373,6 @@ typelibs_

[systemd-devel] [PATCH 03/10] rules: load sg module from 80-drivers.rules

From: Martin Pitt Taken from the Debian specific rules, this is the remaining difference over the upstream 80-drivers.rules. Bug-Debian: http://bugs.debian.org/657948 --- rules/80-drivers.rules | 1 + 1 file changed, 1 insertion(+) diff --git a/rules/80-drivers.rules b/rules/80-drivers.rules i

[systemd-devel] [PATCH 09/10] kmod-static-nodes: condition execution on kmod binary

From: Michael Biebl Creating the list of dead device nodes requires kmod. Inside containers this is not strictly required so we don't want a hard dependency on the kmod package. If the binary does not exist kmod-static-nodes.service will fail, so add a condition to check if the binary is availabl

[systemd-devel] [PATCH 05/10] rules: skip 99-systemd.rules when not running systemd as init

From: Tollef Fog Heen --- rules/99-systemd.rules.in | 1 + 1 file changed, 1 insertion(+) diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in index c3ef81b..df83a38 100644 --- a/rules/99-systemd.rules.in +++ b/rules/99-systemd.rules.in @@ -6,6 +6,7 @@ # (at your option) any lat

[systemd-devel] [PATCH 06/10] tmpfiles: fix permissions of /run/lock and /run/lock/lockdev

From: Tollef Fog Heen --- tmpfiles.d/legacy.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tmpfiles.d/legacy.conf b/tmpfiles.d/legacy.conf index 3219672..a634c17 100644 --- a/tmpfiles.d/legacy.conf +++ b/tmpfiles.d/legacy.conf @@ -10,7 +10,7 @@ # These files are co

[systemd-devel] Misc patches from the Debian systemd package

basing and updating them, so while most the credit goes to the original autors, any blame should fall on me :-P Regards Jon Severinsson ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] [PATCH 07/10] units: order remote-fs.target after local-fs.target

From: Michael Biebl This change was part of the old debianisation branch created by Tollef and reflects the fact that on Debian the $remote_fs system facility depends on $local_fs. --- units/remote-fs.target | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/units/remote-fs.targ

[systemd-devel] [PATCH 02/10] rules: updates to default device permissions in 50-udev-default.rules

From: Martin Pitt Taken from the previous Debian specific rules, this is the remaining difference over the upstream 50-udev-default.rules. --- rules/50-udev-default.rules | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/rules/50-udev-default.rules b/rules/50-ude

[systemd-devel] [PATCH] sysv-generator: do not generate 'Wants' symlinks to generated service files that will be shadowed by a native unit.

--- src/sysv-generator/sysv-generator.c | 29 +++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/src/sysv-generator/sysv-generator.c b/src/sysv-generator/sysv-generator.c index 5206279..aff5fd6 100644 --- a/src/sysv-generator/sysv-generator.c +++ b/src/sy

[systemd-devel] [PATCH] core: collapse JOB_RELOAD on an inactive unit into JOB_NOP

Before this commit systemctl reload on an inactive unit with a queued start job would block until the unit had started if the unit supported reload, but return failure immediately if the unit didn't. Additionally systemctl reload-or-try-restart (and systemctl force-reload) would block until the un

[systemd-devel] [PATCH] build-sys: Do not distribute generated emergency.service

It is already in nodist_systemunit_DATA and if it is shipped, it contains the hardcoded path to systemctl which will cause it to fail to start when rootprefix != prefix and rootbindir != bindir. --- Makefile.am | 1 - 1 file changed, 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index f934

[systemd-devel] [PATCH] Improve xz compression performance.

The new lzma2 compression options at the top of compress_blob_xz are equivalent to using preset "0", exept for using a 1 MiB dictionary (the same as preset "1"). This makes the memory usage at most 7.5 MiB in the compressor, and 1 MiB in the decompressor, instead of the previous 92 MiB in the compr

Re: [systemd-devel] [PATCH 1/2] journal: add LZ4 as optional compressor

xz -0 needs about 3 MiB for compression, hardly a prohibitive requirement. --- jon@ilyena /tmp $ time lz4c -hc systemd-214.tar Compressed filename will be : systemd-214.tar.lz4 Compressed 31436800 bytes into 5120576 bytes ==> 16.29% real0m2.751s user0m2.696s

Re: [systemd-devel] [HEADSUP] New module ‘libc’ in systemd git

On Sun, Mar 31, 2013 at 8:22 PM, Lennart Poettering wrote: > We figured to complete the systemd project we were still lacking an > email program[1] An email program? A web browser immediately strikes me as more important than an email program. That should be our first effort. Of course, an email

Re: [systemd-devel] [PATCH] core: check system call auditing is enabled

ve on, fix the bug, and keep up the good work! :) -Jon ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [PATCH] core: check system call auditing is enabled

On 02/19/2013 03:49 PM, Lennart Poettering wrote: > On Tue, 19.02.13 14:29, Jon Masters (jonat...@jonmasters.org) wrote: > >> From: Jon Masters >> >> Systemd relies upon CONFIG_AUDITSYSCALL support being present in the >> kernel. > > Actually it doesn&

Re: [systemd-devel] [PATCH] core: check system call auditing is enabled

ant systemd to be able to be used in these applications, but it seems to be getting further and further from possible, not closer. Not requiring cgroup controllers was a good first step, and here it seems we're going backwards and requiring AUDITING $0

Re: [systemd-devel] [PATCH] core: check system call auditing is enabled

called on boot that are updated to look for anything that is later needed in procfs and taint somehow. Jon. "Kok, Auke-jan H" wrote: >On Tue, Feb 19, 2013 at 11:29 AM, Jon Masters >wrote: >> From: Jon Masters >> >> Systemd relies upon CONFIG_AUDITSYSCALL su

[systemd-devel] [PATCH] core: check system call auditing is enabled

From: Jon Masters Systemd relies upon CONFIG_AUDITSYSCALL support being present in the kernel. This is because systemd-logind calls audit_session_from_pid, which uses /proc/self/sessionid to determine whether an existing session is being replaced as part of e.g. a call to sudo, pkexec, or

Re: [systemd-devel] One of my fundamental problems with systemd...

On Fri, Oct 26, 2012 at 9:50 PM, Michael H. Warfield wrote: > Excuse me? I'm a kernel maintainer and a member of the Samba team. I > have dedicated almost 2 decades to promoting and developing several > dozen open source projects I will not enumerate here. I don't know or particularly care who