Re: [systemd-devel] Suppressing spam error messages in the system journal

2020-10-19 Thread Michael Biebl
Am Mo., 19. Okt. 2020 um 15:56 Uhr schrieb Lennart Poettering : > > > 2) Could resolved be changed so that this message is only emitted > > (say) once for every 100 or 500 times that the condition is > > detected. > > We actually try hard to suppress unnecessary log lines, but I think > this

Re: [systemd-devel] journald forwarding to rsyslogd. Huge (350 times) performance degradation. What am I doing wrong???

2020-09-21 Thread Michael Biebl
Hm, some performance penalty is certainly expected but 350times slower looks like something is odd. Would be interesting to know, if you can reproduce the performance issue with a more recent version. Afaik, using imuxsock and syslog forwarding should be more performant then imjournal (which was

Re: [systemd-devel] Enable sandboxing options globally for all services

2020-09-09 Thread Michael Biebl
Am Mi., 9. Sept. 2020 um 21:40 Uhr schrieb Christopher Wong : > > Hi, > > > Is there a way to turn on a sandboxing option for all services? Recent versions of systemd allow to use global drop-in config snippets. See the changelog of v244 * Unit files now support top level dropin

Re: [systemd-devel] Need help with setting up systemd for Apache on Debian 10

2020-08-23 Thread Michael Biebl
Am So., 23. Aug. 2020 um 19:20 Uhr schrieb Tom Browder : > I assume the data are correct, and I'm pretty sure there is some > fancy, automated sysstemctl way to get it all working. I would > greatly appreciate some guidance as to how to install the files > correctly. Those files are installed

Re: [systemd-devel] Antw: [EXT] I/O error on "systemctl kill -s HUP rsyslog.service"

2020-08-13 Thread Michael Biebl
Am Do., 13. Aug. 2020 um 09:05 Uhr schrieb Andrei Borzenkov : > > 13.08.2020 09:54, Harald Dunkel пишет: > > On 8/12/20 2:16 PM, Andrei Borzenkov wrote: > >> 12.08.2020 14:03, Harald Dunkel пишет: > >>> See attachment. Hope this helps > >>> Harri > >> > >> > >>> 1 openat(AT_FDCWD, > >>>

Re: [systemd-devel] : How to modify systemd so that the NTP function is disabled when systemd is first started?

2020-04-25 Thread Michael Biebl
Am Sa., 25. Apr. 2020 um 08:52 Uhr schrieb www : > Apr 02 17:24:52 demoboard systemd[1]: System time before build time, > advancing clock. See https://github.com/systemd/systemd/blob/master/src/core/main.c#L1485 or more specifically

Re: [systemd-devel] user service conflict and confusion

2020-04-10 Thread Michael Biebl
Am Fr., 10. Apr. 2020 um 17:59 Uhr schrieb Matt Zagrabelny : > > Greetings, > > I am hitting a confusing scenario with my system. I am running 245.4-2 > (Debian). > > I have a user service, mpd, which is failing to start. It is enabled: > > $ systemctl --user is-enabled mpd > enabled > > And now

Re: [systemd-devel] dockerd broken docker works without It own docker image but need

2020-03-26 Thread Michael Biebl
Am Do., 26. März 2020 um 21:43 Uhr schrieb Dorian ROSSE : > > Do you know the dockerd mailing list? Don't be lazy and find that out yourself. Google (or your search engine of choice) is your friend. ___ systemd-devel mailing list

Re: [systemd-devel] Antw: [EXT] Infinite loop at startup on var fsck failure

2020-02-26 Thread Michael Biebl
Am Mi., 26. Feb. 2020 um 10:13 Uhr schrieb Ulrich Windl : > > >>> Vito Caputo schrieb am 25.02.2020 um 01:01 in > Nachricht > <7343_1582589314_5e546582_7343_4690_1_20200225000143.nowls5peec5sx...@shells.gnu > > eneration.com>: > > Hello list, > > > > Today I experienced an unclean shutdown due to

Re: [systemd-devel] Antw: Re: show journalctl while stopping?

2020-01-24 Thread Michael Biebl
Am Fr., 24. Jan. 2020 um 09:45 Uhr schrieb Ulrich Windl : > Similarly: Before bashing the proposal, why not think about an option that > will enable that feature? Like "--verbose", "--monitor", > "--whatever-you-like"... There you go https://github.com/systemd/systemd/blob/master/TODO#L891

Re: [systemd-devel] Hotplug auto mounting and masked mount units

2020-01-12 Thread Michael Biebl
Am Fr., 10. Jan. 2020 um 17:13 Uhr schrieb Phillip Susi : > > > Lennart Poettering writes: > > > Can you file a bug about this? Sounds like something to fix. > > Sure. https://github.com/systemd/systemd/issues/14550 ___ systemd-devel mailing list

Re: [systemd-devel] Antw: Re: Binary changed since start

2019-12-10 Thread Michael Biebl
There is a tool called needrestart which should do exactly what you want. See https://tracker.debian.org/pkg/needrestart https://github.com/liske/needrestart Am Di., 10. Dez. 2019 um 15:12 Uhr schrieb Ulrich Windl : > > >>> Lennart Poettering schrieb am 10.12.2019 um 12:32 > in > Nachricht

Re: [systemd-devel] need help with undestanding a udev warning

2019-11-16 Thread Michael Biebl
Am Sa., 16. Nov. 2019 um 09:20 Uhr schrieb Andrei Borzenkov : > > Likely result of mass-rewrite in > > commit 25de7aa7b90c23d33ea50ada1e50c5834a414237 > Author: Yu Watanabe > Date: Thu Apr 25 01:21:11 2019 +0200 > > udev: modernize udev-rules.c A bug then? Or is there an error in the udev

[systemd-devel] need help with undestanding a udev warning

2019-11-13 Thread Michael Biebl
Hi, with v243 I get the following warning in my journal: Nov 13 15:38:12 pluto systemd-udevd[319]: /lib/udev/rules.d/90-libgpod.rules:19 IMPORT key takes '==' or '!=' operator, assuming '==', but please fix it. Nov 13 15:38:12 pluto systemd-udevd[319]: /lib/udev/rules.d/90-libgpod.rules:23

Re: [systemd-devel] perform fsck on everyt boot

2019-11-11 Thread Michael Biebl
Am Mo., 11. Nov. 2019 um 16:47 Uhr schrieb Lennart Poettering : > Well, note that ext4's fsck only does an actual file system check > every now and then. Afair this is outdated knowledge. newer e2fsprogs versions no longer setup ext4 file systems to do regular fscks. At least on Debian sid,

Re: [systemd-devel] systemctl stuck when run restart

2019-10-05 Thread Michael Biebl
Am Sa., 5. Okt. 2019 um 17:06 Uhr schrieb Hongyi Zhao : > Type=notify > $ sudo systemctl start ssh > ^C > werner@localhost:~/software/openssh$ sudo systemctl restart ssh > ^C > > If I don't hit ^C, the command will stuck there for ever. I don't think the upstream openssh supports sd_notify. E.g

Re: [systemd-devel] startup hang at 'load/save random seed'

2019-08-07 Thread Michael Biebl
See https://github.com/systemd/systemd/issues/13252 Am Mi., 7. Aug. 2019 um 00:39 Uhr schrieb Chris Murphy : > > [ 10.281769] fmac.local systemd[1]: Starting Update UTMP about > System Boot/Shutdown... > [ 10.295504] fmac.local audit[806]: SYSTEM_BOOT pid=806 uid=0 > auid=4294967295

Re: [systemd-devel] lto issues

2019-08-06 Thread Michael Biebl
Am Di., 6. Aug. 2019 um 09:26 Uhr schrieb Zbigniew Jędrzejewski-Szmek : > > On Sat, Aug 03, 2019 at 07:03:47PM +0200, Michael Biebl wrote: > > Hi, > > > > today I tried compiling systemd v242 (on Debian sid) once using lto > > (-Db_lto=true) and once without lto (-

[systemd-devel] lto issues

2019-08-03 Thread Michael Biebl
Hi, today I tried compiling systemd v242 (on Debian sid) once using lto (-Db_lto=true) and once without lto (-Db_lto=false). The lto build took approximately twice as long on my laptop (using dpkg-buildpackage, which introduces a bit of overhead): lto: real 11m22,605s user 37m9,675s sys

Re: [systemd-devel] systemd-devel listed as support confuses users (was: connection failure)

2019-07-02 Thread Michael Biebl
Am Di., 2. Juli 2019 um 18:52 Uhr schrieb František Šumšal : > This, or since the URL leads to [0], it would be also useful to extend > the "About systemd-devel" section to provide some kind of warning that > this ML is mainly/only for upstream systemd, not for systemd shipped by > distributions.

Re: [systemd-devel] systemd-devel listed as support confuses users (was: connection failure)

2019-07-02 Thread Michael Biebl
Am Di., 2. Juli 2019 um 16:16 Uhr schrieb Paul Menzel : > Reading the output above, I can see, why the people contact this mailing > list. I agree here. While we do have `support-url` which distros can override, Apparently not all of them do. We could probably change our build system, that

Re: [systemd-devel] Antw: Re: Q: Implementing logrotate's postrotate with systemd

2019-06-11 Thread Michael Biebl
Am Di., 11. Juni 2019 um 16:18 Uhr schrieb Reindl Harald : > > > > Am 11.06.19 um 15:00 schrieb Ulrich Windl: > Reindl Harald schrieb am 11.06.2019 um 14:30 in > > Nachricht <917331d8-845f-54d5-908c-e6c7d124a...@thelounge.net>: > >> > >> Am 11.06.19 um 13:34 schrieb Ulrich Windl: > >>> I

Re: [systemd-devel] Antw: Re: Q: Implementing logrotate's postrotate with systemd

2019-06-11 Thread Michael Biebl
Am Di., 11. Juni 2019 um 15:00 Uhr schrieb Ulrich Windl : > > >>> Reindl Harald schrieb am 11.06.2019 um 14:30 in > Nachricht <917331d8-845f-54d5-908c-e6c7d124a...@thelounge.net>: > > > > > Am 11.06.19 um 13:34 schrieb Ulrich Windl: > >> I have a forking service (with a PID file) that can reopen

Re: [systemd-devel] Q: Implementing logrotate's postrotate with systemd

2019-06-11 Thread Michael Biebl
A separate oneshot service sounds like overkill. I would probably use something like `systemctl kill -s HUP ${service}.service` If your sevices spawns multiple processes and you only want to send SIGHUP to the main process, you should add a `--kill-who=main` All documented nicely in

Re: [systemd-devel] Wtrlt: Antw: Re: Can I enable/disable a target?

2019-05-09 Thread Michael Biebl
Am Do., 9. Mai 2019 um 15:52 Uhr schrieb Ulrich Windl : > > (Sorry, I didn't send to the list before) > >>> Ulrich Windl schrieb am 09.05.2019 um > >>> 14:28 > in Nachricht <5cd44cae.ed38.00a...@rz.uni-regensburg.de>: > >>>> Michael Bieb

Re: [systemd-devel] Can I enable/disable a target?

2019-05-09 Thread Michael Biebl
[Please do not send this message to me privately only] Am Do., 9. Mai 2019 um 13:22 Uhr schrieb Ulrich Windl : > > >>> Michael Biebl schrieb am 09.05.2019 um 12:29 in > Nachricht > : > > Am Do., 9. Mai 2019 um 12:27 Uhr schrieb Ulrich Windl > > : > >> &

Re: [systemd-devel] Any defined exit code for a generator?

2019-05-09 Thread Michael Biebl
Am Do., 9. Mai 2019 um 12:29 Uhr schrieb Ulrich Windl : > > Hi! > > The manual page of generators does not talk about exit codes in case of an > error. Is there any handling of exit codes in systemd? exit codes > 0 returned by the generator are treated as errors and systemd will log about this

Re: [systemd-devel] Can I enable/disable a target?

2019-05-09 Thread Michael Biebl
Am Do., 9. Mai 2019 um 12:27 Uhr schrieb Ulrich Windl : > > Hi! > > Whenever I try to enable or disable a target (that exists), I get "Failed to > execute operation: No such file or directory". What file or directory, > please? Or what is the command trying to say? Can you share the target unit

Re: [systemd-devel] Arbitrary restrictions (e.g. for RuntimeDirectory)

2019-05-09 Thread Michael Biebl
Hi Am Do., 9. Mai 2019 um 12:22 Uhr schrieb Ulrich Windl : > Despite of that I'm missing a "systemctl validate ..." command. That way I > wouldn't need to execute start, status, stop, just to find out that some > settings are rejected. There is "systemd-analyze verify". -- Why is it that

Re: [systemd-devel] Again, why this strange behavior implied by "auto" in fstab ?

2019-04-30 Thread Michael Biebl
Am Di., 30. Apr. 2019 um 11:20 Uhr schrieb Franck Bui : > Just in case, this "feature" has been finally removed since v242 (commit > 42b8142d7). I can't find a commit with that id https://github.com/systemd/systemd/commit/42b8142d7 -- Why is it that all of the instruments seeking intelligent

Re: [systemd-devel] Build only libsystemd as a shared library

2019-04-23 Thread Michael Biebl
Am Di., 23. Apr. 2019 um 17:51 Uhr schrieb Stanislav Angelovič : > > Hi systemd-ers, > > Having recent systemd sources, how can I build libsystemd.so only? > > I was able to build the static version with this: > meson build/ > ninja -C build version.h > ninja -C build libsystemd.a > > But how can

Re: [systemd-devel] umount NFS problem

2019-04-05 Thread Michael Biebl
Am Fr., 5. Apr. 2019 um 08:45 Uhr schrieb Mantas Mikulėnas : > The job order (home.mount vs nfs-client.target) already looks correct, so > fstab options probably won't help much; I'd try to ensure that the umount > doesn't fail in the first place. > > Normally I'd expect user sessions

Re: [systemd-devel] systemd prerelease 242-rc2

2019-04-04 Thread Michael Biebl
fwiw, in Debian we added https://salsa.debian.org/systemd-team/systemd/commit/b274b4ad5a4ba543c8c013fb71dacf2467030ddc Am Do., 4. Apr. 2019 um 21:39 Uhr schrieb Mike Gilbert : > > On Thu, Apr 4, 2019 at 3:38 PM Mike Gilbert wrote: > > > > On Thu, Apr 4, 2019 at 11:23 AM Lennart Poettering > >

Re: [systemd-devel] looking for help to resolve shutdown problem

2019-04-04 Thread Michael Biebl
Am Do., 4. Apr. 2019 um 11:27 Uhr schrieb Michael Biebl : > > Am Do., 4. Apr. 2019 um 09:16 Uhr schrieb Harald Dunkel > : > > https://freedesktop.org/wiki/Software/systemd/Debugging/ > > > > The promised /shutdown-log.txt file was not created (or I was too > &

Re: [systemd-devel] looking for help to resolve shutdown problem

2019-04-04 Thread Michael Biebl
Am Do., 4. Apr. 2019 um 09:16 Uhr schrieb Harald Dunkel : > https://freedesktop.org/wiki/Software/systemd/Debugging/ > > The promised /shutdown-log.txt file was not created (or I was too > blind to see). If systemd was compiled for a split-usr system (like in Debian/Ubuntu), the script

Re: [systemd-devel] WantedBy=default.target

2019-03-07 Thread Michael Biebl
Am Do., 7. März 2019 um 15:47 Uhr schrieb Zbigniew Jędrzejewski-Szmek : > > On Thu, Mar 07, 2019 at 11:31:18AM +0100, Michael Biebl wrote: > > Am Do., 7. März 2019 um 11:24 Uhr schrieb Lennart Poettering > > : > > > > > > On Do, 07.03.19 10:30, Mi

Re: [systemd-devel] WantedBy=default.target

2019-03-07 Thread Michael Biebl
Am Do., 7. März 2019 um 11:24 Uhr schrieb Lennart Poettering : > > On Do, 07.03.19 10:30, Michael Biebl (mbi...@gmail.com) wrote: > > > Looks like quite a few services use > > WantedBy=default.target > > https://codesearch.debian.net/search?q=WantedBy%3Ddefault.target &g

[systemd-devel] WantedBy=default.target

2019-03-07 Thread Michael Biebl
Looks like quite a few services use WantedBy=default.target https://codesearch.debian.net/search?q=WantedBy%3Ddefault.target Some of them are user services, but I wonder if there is recommendation regarding system services. Should they use multi-user.target or graphical.target instead or is it ok

[systemd-devel] taking time off

2019-01-15 Thread Michael Biebl
Will stop maintaining systemd in debian for a while. What's going on is just too stupid/crazy. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list

Re: [systemd-devel] GithHub / private repos

2019-01-09 Thread Michael Biebl
Am Mi., 9. Jan. 2019 um 21:24 Uhr schrieb Michael Biebl : > > https://blog.github.com/2019-01-07-new-year-new-github/ > > might be of interest given the recent discussions how to handle security > issues. Answering to myself: With the restriction of 3 developers per private r

[systemd-devel] GithHub / private repos

2019-01-09 Thread Michael Biebl
https://blog.github.com/2019-01-07-new-year-new-github/ might be of interest given the recent discussions how to handle security issues. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Re: [systemd-devel] Disable message "A start job is running for myservice"

2018-12-10 Thread Michael Biebl
Am Mo., 10. Dez. 2018 um 14:26 Uhr schrieb Lennart Poettering : > > On Mo, 10.12.18 13:47, Paolo Minazzi (paolo.mina...@mitrol.it) wrote: > > > but these parameter cannot modify the behaviour. > > Is there some way to do it ? > > No there is not. This is compiled in and global. You can turn off

Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)

2018-11-10 Thread Michael Biebl
Am Sa., 10. Nov. 2018 um 20:04 Uhr schrieb Michael Biebl : > ... in Debian, to be clear. I updated https://wiki.debian.org/Teams/pkg-systemd/Packaging#systemd_unit_files_naming_and_installation a bit. Hope it's helpful. Let me know if it needs further clarifications. Michael --

Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)

2018-11-10 Thread Michael Biebl
Am Sa., 10. Nov. 2018 um 19:59 Uhr schrieb Michael Biebl : > > Am Sa., 10. Nov. 2018 um 19:56 Uhr schrieb Michael Biebl : > > > > My recommendation would be, to not create the myslq(d).service alias > > dynamically via > > [Install] > > Alias=mysql.service >

Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)

2018-11-10 Thread Michael Biebl
Am Sa., 10. Nov. 2018 um 19:56 Uhr schrieb Michael Biebl : > > My recommendation would be, to not create the myslq(d).service alias > dynamically via > [Install] > Alias=mysql.service > Alias=mysqld.service > > but ship it as a static symlink in the package As an example

Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)

2018-11-10 Thread Michael Biebl
Am Sa., 10. Nov. 2018 um 19:53 Uhr schrieb Faustin Lammler : > > Hi, > sorry if this was already discussed but I can't find any > pointer or documentation on how to handle this. > > This is the problem we are facing: > https://jira.mariadb.org/browse/MDEV-15526 > > It can be reproduced on Debian

Re: [systemd-devel] reliable way to check if udev is ready to serve requests

2018-10-11 Thread Michael Biebl
Am Do., 11. Okt. 2018 um 08:54 Uhr schrieb Lennart Poettering : > > On Di, 09.10.18 22:24, Michael Biebl (mbi...@gmail.com) wrote: > > > Hi, > > > > is there a reliable way to check from a shell script that udevd is > > running and able to serve request? > &g

[systemd-devel] reliable way to check if udev is ready to serve requests

2018-10-09 Thread Michael Biebl
Hi, is there a reliable way to check from a shell script that udevd is running and able to serve request? Say you want to run "udevadm trigger" but only if udevd is actually able to process that request. There is a udev_ctrl_send_ping() function, which looks like it could be perhaps used for

Re: [systemd-devel] Revert "meson: use the host architecture compiler/linker for src/boot/efi" #10217

2018-09-30 Thread Michael Biebl
Am So., 30. Sep. 2018 um 19:57 Uhr schrieb Helmut Grohne : > I filed this build failure almost two months ago, see > https://bugs.debian.org/905381. And the meson maintainer had me wait > since April (close to when the breaking commit was introduced) to add > the relevant tools to the cross file

Re: [systemd-devel] exim4 only queues mails sent by systemd service

2018-09-24 Thread Michael Biebl
Am So., 23. Sep. 2018 um 22:49 Uhr schrieb Kamil Jońca : > > It is something strange with sending mails from systemd system service: > assume we have service file /etc/systemd/system/mailtest.service: > > --8<---cut here---start->8--- > [Unit] >

Re: [systemd-devel] blocking service on shutdown

2018-09-05 Thread Michael Biebl
Am Di., 4. Sep. 2018 um 18:53 Uhr schrieb Ralf Sieger : > > Well, it does wait when I press the power button on the case. > It does not wait if I enter as root poweroff or reboot. > I assume the first one goes through the logind while the second case does > straight to systemd... > You are

Re: [systemd-devel] blocking service on shutdown

2018-09-04 Thread Michael Biebl
2018-09-04 18:17 GMT+02:00 Ralf Sieger : > Hi Michael, > > this solution has a couple of drawbacks: > - block will let shutdown, etc. fail, I do only need a pause/wait > - delay does not work with reboot It should work for shutdown, i.e. reboot. -- Why is it that all of the instruments seeking

Re: [systemd-devel] blocking service on shutdown

2018-09-02 Thread Michael Biebl
2018-09-02 15:37 GMT+02:00 Ralf Sieger : > Hi, > > I want my system to pause on shutdown to wait till my backup has finished if > it is running. I would suggest using an inhibitor lock when running your backup. See https://www.freedesktop.org/wiki/Software/systemd/inhibit/ That's exactly the

Re: [systemd-devel] Select on value of log message

2018-08-30 Thread Michael Biebl
I don't want to use systemd as a stick to beat people^maintainers with Am Do., 30. Aug. 2018 um 18:56 Uhr schrieb Uoti Urpala : > > On Thu, 2018-08-30 at 16:39 +0200, Michael Biebl wrote: > > Am Do., 30. Aug. 2018 um 15:50 Uhr schrieb Jérémy Rosen < > > jeremy.ro...@smil

Re: [systemd-devel] Select on value of log message

2018-08-30 Thread Michael Biebl
Am Do., 30. Aug. 2018 um 15:50 Uhr schrieb Jérémy Rosen < jeremy.ro...@smile.fr>: > I *think* that it's deactivated in debian because journalctl is a core > package and debian doesn't want to pull the regex library into it's core... > Right, no need to file another bug report.

Re: [systemd-devel] udev script can't resolve host name

2018-08-15 Thread Michael Biebl
Am Mi., 15. Aug. 2018 um 11:09 Uhr schrieb Jonathan Kamens : > > Hi, > > If I understand correctly, this mailing list can be used for questions about > udev as well as about systemd. If that's not correct, somebody please let me > know and I will go elsewhere (and if you know where that

Re: [systemd-devel] Best way to run upstream systemd

2018-07-18 Thread Michael Biebl
2018-07-19 1:46 GMT+02:00 Ryan Gonzalez : > The fastest any distro is going to get systemd would probably be from a > bleeding-edge distro (e.g. Fedora Rawhide). If you don't want you system to > be a disaster zone, though, Arch got systemd 237 just two weeks after > release. > > Fedora will push

Re: [systemd-devel] upower fails with PrivateNetwork=true

2018-07-07 Thread Michael Biebl
2018-07-06 13:23 GMT+02:00 Lennart Poettering : > Yes, Mantas is right, PrivateNetwork= disconnects the whole of > AF_NETLINK from the rest of the system, which means services that > require libudev device events can't use it. Thank you Lennart and Mantas. I was indeed not aware that

[systemd-devel] upower fails with PrivateNetwork=true

2018-07-05 Thread Michael Biebl
Hi, in the latest upower release 0.99.8, the systemd service file was locked down considerably[1]. Unfortunately, a result of that is, that upower no longer detects any plug/unplug events [2]. Through some trial and error I found that it's the addition of PrivateNetworks=true which broke upower.

Re: [systemd-devel] How to build only udev

2018-07-04 Thread Michael Biebl
arm64 is on a different archive in Ubuntu. You'll need to add deb [arch=arm64] http://ports.ubuntu.com/ xenial main universe to your /etc/apt/sources.list After an "apt update", libudev-dev:arm64 should be available. 2018-07-04 21:42 GMT+02:00 Kevin Greene : > Thanks Simon. I have tried doing

Re: [systemd-devel] How to guarantee the stdout buffer between systemd and journald is flushed when program quits?

2018-05-17 Thread Michael Biebl
2018-05-17 23:02 GMT+02:00 Ivan Kurnosov : > Here is the example of the `journald` output for the service: I assume you used journalctl -u bla.service? If so, do the log messages turn up if you run journalctl? Then this might be another instance of

Re: [systemd-devel] Running “telinit u” on glibc update

2018-05-16 Thread Michael Biebl
Hi Florian 2018-05-16 15:01 GMT+02:00 Florian Weimer : > In Fedora, for historic reasons, we run “/sbin/telinit u” after installing a > new glibc RPM package version. > > Does this still make sense? Should we remove the code which invokes telinit > from the glibc package? We

[systemd-devel] "CVE-2013-4392: TOCTOU race condition when updating file permissions and SELinux security contexts" still an issue

2018-03-24 Thread Michael Biebl
Hi, the Debian systemd package has an open bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725357 about CVE-2013-4392: TOCTOU race condition when updating file permissions and SELinux security contexts This references https://bugzilla.redhat.com/show_bug.cgi?id=859060 which never

Re: [systemd-devel] systemd-shutdown: Failed to parse /proc/self/moutinfo

2018-03-13 Thread Michael Biebl
My problem is sooo important, I need to pester the whole systemd-devel mailing list with a regular bug report. 2018-03-13 16:54 GMT+01:00 Reindl Harald : > see https://bugzilla.redhat.com/show_bug.cgi?id=1554943 including screenshot >

Re: [systemd-devel] Hints for upgrading systemd on a running system

2018-02-20 Thread Michael Biebl
2018-02-20 20:00 GMT+01:00 Paul Menzel : > > Do I need to stop those manually beforehand, or is there another way to > clean up? reboot. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Re: [systemd-devel] how to debug failures when trying to lock down services

2017-12-01 Thread Michael Biebl
2017-11-30 18:24 GMT+01:00 Lennart Poettering : > On Do, 30.11.17 10:35, Mantas Mikulėnas (graw...@gmail.com) wrote: > >> Then I'm guessing ProtectSystem=strict overrides ReadWritePaths and makes >> /var/log read-only... > > Hmm, it does? It really shouldn't. > > I thought

Re: [systemd-devel] how to debug failures when trying to lock down services

2017-11-30 Thread Michael Biebl
2017-11-30 16:07 GMT+01:00 Michael Biebl <mbi...@gmail.com>: > 2017-11-30 9:35 GMT+01:00 Mantas Mikulėnas <graw...@gmail.com>: >> On Thu, Nov 30, 2017 at 10:31 AM, Michael Biebl <mbi...@gmail.com> wrote: >>> >>> 2017-11-30 6:52 GMT+01:00 Mantas Mikulė

Re: [systemd-devel] how to debug failures when trying to lock down services

2017-11-30 Thread Michael Biebl
2017-11-30 6:52 GMT+01:00 Mantas Mikulėnas <graw...@gmail.com>: > On Thu, Nov 30, 2017 at 5:27 AM, Michael Biebl <mbi...@gmail.com> wrote: >> >> Hi, >> >> today I tried to lock down the rsyslog.service that I have on my system. >> >> For t

[systemd-devel] how to debug failures when trying to lock down services

2017-11-29 Thread Michael Biebl
Hi, today I tried to lock down the rsyslog.service that I have on my system. For that I first created an override.conf that contained [Service] ProtectHome=yes PrivateTmp=yes PrivateDevices=yes ProtectSystem=strict ReadWritePaths=/var/log ReadWritePaths=/var/spool/rsyslog

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Michael Biebl
2017-11-20 19:26 GMT+01:00 Michael Biebl <mbi...@gmail.com>: > https://anonscm.debian.org/git/pkg-systemd/systemd.git/commit/debian/extra/pam.d/systemd-user?id=b3238e9604fa61c7ec45a2d0acc1f8b40728cd87 > > This might be relevant to you. > > See how the pam confi

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Michael Biebl
https://anonscm.debian.org/git/pkg-systemd/systemd.git/commit/debian/extra/pam.d/systemd-user?id=b3238e9604fa61c7ec45a2d0acc1f8b40728cd87 This might be relevant to you. See how the pam config contains pam_limits 2017-11-20 18:49 GMT+01:00 Lennart Poettering : > On Mo,

Re: [systemd-devel] Is there a way to override the "Where" option in mount units?

2017-11-01 Thread Michael Biebl
2017-11-01 11:40 GMT+01:00 Michael Biebl <mbi...@gmail.com>: > See > https://anonscm.debian.org/cgit/collab-maint/nfs-utils.git/tree/debian/patches/24-systemd-pipefs_in_run.patch?h=debian/sid Also requires https://anonscm.debian.org/cgit/collab-maint/nfs-utils.git/tree/debian/pat

Re: [systemd-devel] Is there a way to override the "Where" option in mount units?

2017-11-01 Thread Michael Biebl
2017-11-01 10:56 GMT+01:00 Lennart Poettering : > > Hmm, rpc_pipefs is a virtual API fs, right? If so, it really shouldn't > be mounted below /var in the first place. Any chance you can work with > the NFS folks to maybe move it below /run (or /sys or so) where API > file

Re: [systemd-devel] Conflicts no longer working as expected during boot in v235

2017-10-14 Thread Michael Biebl
Ok, the problem is apparently happening because spice-vdagent triggers the start of a service via a udev rule. In a minimal Debian buster installation, which does not exhibit the problem, I can trigger the problem after adding the following two files: # cat /etc/systemd/system/sleep.service

Re: [systemd-devel] Conflicts no longer working as expected during boot in v235

2017-10-14 Thread Michael Biebl
After investigating this further, I can also reproduce this with older systemd versions (tested with v232 and v234). For the problem to be reproducible, I had to install spice-vdagent in the libvirt/KVM instance. Haven't quite figured out yet how this influences the start of chrony.service and

Re: [systemd-devel] Conflicts no longer working as expected during boot in v235

2017-10-13 Thread Michael Biebl
This is 100% reproducible here, fwiw. Both services are always started after a reboot. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list

[systemd-devel] Conflicts no longer working as expected during boot in v235

2017-10-13 Thread Michael Biebl
Hi, in Debian we enable systemd-timesyncd by default. A while ago, I decided to install chrony. The chrony.service file has Conflicts=systemd-timesyncd.service. In the past this was sufficient to ensure that only chrony is started. After the upgrade to v235 I now see this: $ systemctl status

Re: [systemd-devel] Store journal logs to different journals(location) based on Filters

2017-09-20 Thread Michael Biebl
2017-09-20 8:13 GMT+02:00 P.R.Dinesh : > Is it possible to store journal logs matching specific filters to different > journal files in addition to the main journal using some journald > configurations? No > For eg., All journal logs of severity critical and above should be

Re: [systemd-devel] question about system reboot and shutdown

2017-08-09 Thread Michael Biebl
2017-08-09 14:51 GMT+02:00 Marek Floriańczyk : > Dnia środa, 9 sierpnia 2017 11:51:07 CEST Tilman Baumann pisze: >> On 09.08.2017 11:28, Tilman Baumann wrote: > > NUT looks like quite active based on their website. > Microupsd daemon handles also some switches and leds

Re: [systemd-devel] /etc/systemd/system/default.target.wants/ no longer checked for unit files

2017-07-14 Thread Michael Biebl
2017-07-14 12:24 GMT+02:00 Mantas Mikulėnas : > On Fri, Jul 14, 2017 at 12:13 PM, Richard W.M. Jones > wrote: >> >> >> https://github.com/systemd/systemd/issues/6334 >> >> Since this commit >> >>

Re: [systemd-devel] udev rule to mount ext4 with data=journal

2017-06-14 Thread Michael Biebl
2017-06-14 10:44 GMT+02:00 Pascal K : > As I am on a embedded device I am trying to avoid the usage of systemd due > to serveral reasons. Does that mean you are not using systemd as PID 1? -- Why is it that all of the instruments seeking intelligent life in the universe

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

2017-06-06 Thread Michael Biebl
2017-06-06 20:07 GMT+02:00 Steve Dickson : > Finally, the whole idea of systemd randomly/silently > strip off mount options is crazy... IMHO... Personally, I would prefer if systemd simply logged a warning/error message but would *not* strip the bg option. -- Why is it that

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

2017-05-30 Thread Michael Biebl
2017-05-30 10:55 GMT+02:00 NeilBrown <ne...@suse.com>: > On Tue, May 30 2017, Michael Biebl wrote: > >> 2017-05-30 0:19 GMT+02:00 NeilBrown <ne...@suse.com>: >> >>> +.B bg >>> +option is not supported, and may be stripped from the option list. &

Re: [systemd-devel] [PATCH] nfs.man: document incompatibility between "bg" option and systemd.

2017-05-30 Thread Michael Biebl
2017-05-30 0:19 GMT+02:00 NeilBrown : > +.B bg > +option is not supported, and may be stripped from the option list. Either systemd is updated to actually strip the bg option or not. The documentation should reflect that. I don't think we should be vague about this, as it would

Re: [systemd-devel] [systemd-nspawn] machinectl pull-tar fails because importd it not installed

2017-05-13 Thread Michael Biebl
Make sure to pass --enable-importd to ./configure. Also, looking at Makefile.am, you see that importd is built conditionally: if ENABLE_IMPORTD if HAVE_LIBCURL if HAVE_XZ if HAVE_ZLIB if HAVE_BZIP2 if HAVE_GCRYPT ... So, you need to have the devel packages for curl, xz/lzma, zlib, bzip2 and

Re: [systemd-devel] start user-service only with UID greater than 1000

2017-05-09 Thread Michael Biebl
Afaics, the logind/PAM session for gdm/Debian-gdm is deliberate. gdm spawns that via gdm-launch-environment, see /etc/pam.d/gdm-launch-environment, which in turn includes pam_systemd.so 2017-05-09 20:35 GMT+02:00, Lennart Poettering : > On Tue, 09.05.17 17:06, Jakob Schürz

Re: [systemd-devel] nspawn: devpts not mounted with PrivateUsers

2017-04-20 Thread Michael Biebl
2017-04-20 13:09 GMT+02:00 Michael Biebl <mbi...@gmail.com>: > nspawn/machined are in the systemd-container package in Debian, which > in turn recommends libnss-mymachines. > Recommends are installed by default, unless the user explicitly disables that. And libnss-mymachines dep

Re: [systemd-devel] nspawn: devpts not mounted with PrivateUsers

2017-04-20 Thread Michael Biebl
2017-04-20 12:32 GMT+02:00 Lennart Poettering : > On Thu, 20.04.17 00:14, Olaf the Lost Viking (olaf.the.lost.vik...@gmail.com) > wrote: > >> > Don't do this. If you register the group like this, nspawn will >> > normally abstain from using this group. Use "nss-mymachines"

Re: [systemd-devel] My experience with MySQL and systemctl

2017-04-12 Thread Michael Biebl
2017-04-12 20:24 GMT+02:00 Tomasz Torcz : > On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote: >> The right (or, better) solution IMHO would be for mysqld to signal to >> systemd that it's running OK before recovery starts, using type=notify. >> This way recovery can

Re: [systemd-devel] Any reason why /run and /dev/shm do not have MS_NOEXEC flags set?

2017-02-01 Thread Michael Biebl
2017-02-01 11:02 GMT+01:00 Hoyer, Marko (ADITG/SW2) : > - Is there any reason why the mount points /run and /dev/shm do not have > MS_NOEXEC flags set? /run → https://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/ the initrd can place executables in /run so it

Re: [systemd-devel] About http://0pointer.net/blog/avoiding-cve-2016-8655-with-systemd.html

2016-12-08 Thread Michael Biebl
You are confusing a user service (which is installed in /usr/lib/systemd/user) with priviledge dropping via User=. Those are different things. 2016-12-09 2:01 GMT+01:00 Reindl Harald <h.rei...@thelounge.net>: > > > Am 09.12.2016 um 01:56 schrieb Michael Biebl: >> >>

Re: [systemd-devel] About http://0pointer.net/blog/avoiding-cve-2016-8655-with-systemd.html

2016-12-08 Thread Michael Biebl
would annotate in the man page, which sandboxing features work for user services and which don't. It's not always immediately obvious which feature requires root privileges. Michael 2016-12-09 1:46 GMT+01:00 Michael Biebl <mbi...@gmail.com>: > Reading Lennarts recent blog post, I ju

[systemd-devel] About http://0pointer.net/blog/avoiding-cve-2016-8655-with-systemd.html

2016-12-08 Thread Michael Biebl
Reading Lennarts recent blog post, I just wanted to make people aware that the RestrictAddressFamilies= feature is currently broken on several architectures, including i386. So be careful for now until https://github.com/systemd/systemd/issues/4575 has been fixed -- Why is it that all of the

Re: [systemd-devel] Strange output of `systemd-analyze critical-chain`

2016-11-15 Thread Michael Biebl
systemd-analyze and systemd-analyze critical-chain output can be misleading sometimes. Would it be possible for you to install systemd-bootchart. This will give you a much better picture of which process uses IO/CPU ressources. 2016-11-15 21:40 GMT+01:00 Paul Menzel

[systemd-devel] journal files interoperability between distros wrt compression

2016-11-09 Thread Michael Biebl
Hi, currently, when trying to opan a Fedora journal file from Debian/Ubuntu I get: Journal file .../system.journal uses an unsupported feature, ignoring file. This is probably due to Debian not having lz4 support enabled (yet). We currently only build with XZ compression. I wonder what other

Re: [systemd-devel] Query regarding NOTIFY_SOCKET

2016-11-08 Thread Michael Biebl
I suggest reading https://www.freedesktop.org/software/systemd/man/daemon.html It's not necessary to fork for a new-style daemon and actually discouraged. 2016-11-08 14:28 GMT+01:00 Raghavendra. H. R : > Hi Tomasz, > > Thanks for pointing out the mistake. I actually missed

Re: [systemd-devel] rpcbind.socket failing

2016-10-31 Thread Michael Biebl
Why is it using /var/run (where /var could be on a separate partition) and not /run for the socket files? 2016-10-31 18:19 GMT+01:00 Steve Dickson : > Hello, > > Upstream has come up with some new rpcbind service socket files > and I'm trying to incorporate them into f25. > >

[systemd-devel] bus1, dbus(-daemon) and systemd

2016-10-01 Thread Michael Biebl
Hi, I've been watching the bus1 presentation from this years systemd.conf (thanks a lot for the video team btw for doing a stellar job). What didn't become clear to me i, how bus1, dbus(-daemon) and systemd are supposed to fit together in the future. If I understood David correctly, bus1 is not

[systemd-devel] why do we have aliases fro timedated, resolved, networkd, and what are they good for?

2016-09-09 Thread Michael Biebl
Hi I wonder why we have the following aliases/symlinks dbus-org.freedesktop.hostname1.service -> systemd-hostnamed.service dbus-org.freedesktop.import1.service -> systemd-importd.service dbus-org.freedesktop.locale1.service -> systemd-localed.service dbus-org.freedesktop.login1.service ->

Re: [systemd-devel] RFC: removing .shapshot

2016-07-22 Thread Michael Biebl
Hi 2015-11-07 14:33 GMT+01:00 Zbigniew Jędrzejewski-Szmek : > Hi, > > do you use .snapshot unit type? If you do, please speak up. > > I'd like to remove support for the .snapshot unit type. > It seems not be used, snapshots are basically transient targets, > and targets can be

  1   2   3   4   5   6   >