Re: [systemd-devel] Normal user can ask status of services

Am Sa., 26. Aug. 2023 um 15:25 Uhr schrieb Andrei Borzenkov : > > On 26.08.2023 15:46, Michael Biebl wrote: > > > > Reading system logs is a privileged operation. > > > > It is not about reading logs but about being able to "systemctl status > some-sys

Re: [systemd-devel] Normal user can ask status of services

Am Sa., 26. Aug. 2023 um 09:44 Uhr schrieb Cecil Westerhof : > > I am at last implementing systemd timers. The service I created can have its > status queried by a normal user. I thought I must have made a mistake. But > when I do: > systemctl status cron > > I get: > ● cron.service -

Re: [systemd-devel] Splitting large message written to stdout, explanation?

Am So., 21. Mai 2023 um 18:26 Uhr schrieb Stephen Hemminger : > Syslog was never really intended for large size messages. It is not Windows > event log. > If you are sending large complex things then using dbus to communicate > directly > is a better option. dbus is not a suitable protocol for

Re: [systemd-devel] systemctl daemon-reexec forgets running services and starts everything new

Am Mo., 10. Apr. 2023 um 09:46 Uhr schrieb Mantas Mikulėnas : > > On Tue, Apr 4, 2023 at 11:33 AM Wasser, Erik wrote: >> >> # Some details to the hardware # >> >> Our metal runs OpenVZ/Virtuozzo with this kernel (without any problems): >> >> > Linux FQDN_REDACTED 3.10.0-1127.18.2.vz7.163.46 #1

Re: [systemd-devel] Smooth upgrades for socket activated services

Am Mo., 20. Feb. 2023 um 11:06 Uhr schrieb Mike Hearn : > > Hi, > > I'm exploring socket activation as part of work on a tool that makes > systemd-controlled servers easier to deploy and use. Given a config > file the tool builds a package that contains the app and systemd > units, uploads it,

Re: [systemd-devel] systemd-stable and Debian's systemd release strategy

And as always: help is more then welcome. If you want to get involved, please contact us at #debian-systemd on OFTC Am Mi., 18. Jan. 2023 um 16:57 Uhr schrieb Michael Biebl : > > Quite simple: > stable releases: Debian policy is rather strict regarding stable > uploads and some of

Re: [systemd-devel] systemd-stable and Debian's systemd release strategy

Quite simple: stable releases: Debian policy is rather strict regarding stable uploads and some of the changes that landed in systemd-stable are not really considered suitable for a stable upload to Debian. That's why we only cherry-pick select fixes. If the Debian policy was more lax in that

Re: [systemd-devel] Antw: [EXT] [systemd???devel] starting networking from within single user mode?

Yeah, can we please block this Ulrich Windl guy. He's been more of a nuisance than a benefit to this community. Am Mo., 14. Nov. 2022 um 09:17 Uhr schrieb Mantas Mikulėnas : > > On Mon, Nov 14, 2022 at 9:00 AM Ulrich Windl > wrote: >> >> >>> Mantas Mikulenas schrieb am 11.11.2022 um 15:49 in

Re: [systemd-devel] systemd-container: Trying to use a bookworm chroot with a buster host fails / Failed to create /init.scope control group

:38 Uhr schrieb Michael Biebl : > > What are you Missing? > > Lennart Poettering schrieb am So., 16. Okt. 2022, > 23:45: >> >> On So, 16.10.22 21:02, Michael Biebl (mbi...@gmail.com) wrote: >> >> > Am So., 16. Okt. 2022 um 16:23 Uhr schrieb Lennart Poetteri

Re: [systemd-devel] systemd-container: Trying to use a bookworm chroot with a buster host fails / Failed to create /init.scope control group

What are you Missing? Lennart Poettering schrieb am So., 16. Okt. 2022, 23:45: > On So, 16.10.22 21:02, Michael Biebl (mbi...@gmail.com) wrote: > > > Am So., 16. Okt. 2022 um 16:23 Uhr schrieb Lennart Poettering > > : > > > > > > On Fr, 14.10.22 22:57, Mi

Re: [systemd-devel] systemd-container: Trying to use a bookworm chroot with a buster host fails / Failed to create /init.scope control group

Am So., 16. Okt. 2022 um 16:23 Uhr schrieb Lennart Poettering : > > On Fr, 14.10.22 22:57, Michael Biebl (mbi...@gmail.com) wrote: > > > Hi, > > > > since the issue came up on the Debian bug tracker at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019147 ,

[systemd-devel] systemd-container: Trying to use a bookworm chroot with a buster host fails / Failed to create /init.scope control group

Hi, since the issue came up on the Debian bug tracker at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019147 , I figured I ask here: Am 04.09.22 um 18:40 schrieb Bernhard Übelacker: > > Package: systemd-container > Severity: wishlist > X-Debbugs-Cc: bernha...@mailbox.org > > > Dear

Re: [systemd-devel] Is it possible to let systemd create a listening socket and yet be able to have that socket activate nothing, at least temporarily?

Am Fr., 7. Okt. 2022 um 09:24 Uhr schrieb Klaus Ebbe Grue : > QUESTION: Is it possible to let systemd create a listening socket and yet be > able to have that socket activate nothing, at least temporarily? Unfortunately not. You'd need some kind of "maintenance" mode you could put a service in,

Re: [systemd-devel] *****SPAM***** Re: problem understanding why I am 'forced' to run systemd-journald

Am Mi., 5. Okt. 2022 um 13:28 Uhr schrieb František Šumšal : > > On 10/5/22 11:56, Marc wrote: > > I have seen that, but is that not something like 'accepting log entries and > > sending data to /dev/null'? I am looking for an option that does not > > process anything. > > Not really, as the man

Re: [systemd-devel] problem understanding why I am 'forced' to run systemd-journald

https://www.freedesktop.org/software/systemd/man/journald.conf.html#Storage= → volatile Am Mi., 5. Okt. 2022 um 11:40 Uhr schrieb Marc : > > > Hello, > > I have started to upgrade a few machines from CentOS7 to recent versions of > CentOS/Rocky. However I don't really get why there is a

Re: [systemd-devel] Antw: Re: Re: [EXT] Re: Q: Querying units for "what provides" a target

Am Fr., 9. Sept. 2022 um 14:12 Uhr schrieb Michael Biebl : > > Am Fr., 9. Sept. 2022 um 14:01 Uhr schrieb Ulrich Windl > : > > > > >>> Andrei Borzenkov schrieb am 09.09.2022 um 13:41 in > > Nachricht > > : > > > On Fr

Re: [systemd-devel] Antw: Re: Re: [EXT] Re: Q: Querying units for "what provides" a target

Am Fr., 9. Sept. 2022 um 14:01 Uhr schrieb Ulrich Windl : > > >>> Andrei Borzenkov schrieb am 09.09.2022 um 13:41 in > Nachricht > : > > On Fri, Sep 9, 2022 at 2:13 PM Ulrich Windl > > wrote: > > ... > >> > > >> > If you are interested in services that pull in e.g. time-sync.target > >> > via

Re: [systemd-devel] [EXT] Re: Q: Querying units for "what provides" a target

Am Fr., 9. Sept. 2022 um 12:31 Uhr schrieb Michael Biebl : > > Am Fr., 9. Sept. 2022 um 12:08 Uhr schrieb Ulrich Windl > : > > > > >>> Michael Biebl schrieb am 09.09.2022 um 10:55 in > > Nachricht > > : > > > Example: syslog.se

Re: [systemd-devel] [EXT] Re: Q: Querying units for "what provides" a target

Am Fr., 9. Sept. 2022 um 12:08 Uhr schrieb Ulrich Windl : > > >>> Michael Biebl schrieb am 09.09.2022 um 10:55 in > Nachricht > : > > Example: syslog.service > > > > $ systemctl status syslog.service > > ● rsyslog.service - System Logging Service

Re: [systemd-devel] [EXT] Re: Q: Querying units for "what provides" a target

that syslog.service is provided by provided by rsyslog.service (and the actual name of the file on the disk) Isn't this what you wanted? If not, I must have misunderstood what you are looking for. Am Fr., 9. Sept. 2022 um 10:52 Uhr schrieb Ulrich Windl : > > >>> Michael Biebl schrie

Re: [systemd-devel] Q: Querying units for "what provides" a target

I'd probably just use `systemctl status` Am Fr., 9. Sept. 2022 um 10:18 Uhr schrieb Ulrich Windl : > > Hi! > > I'm wondering: having some specific target, e.g. time-set.target, how can I > find out what actually "provides" that target? > I see that I can query what "requires" the given target,

Re: [systemd-devel] Help required for configuring a blocking service during shutdown

Would the systemd inhibit interface be an option? https://www.freedesktop.org/wiki/Software/systemd/inhibit/ It was designed for that use case after all. Am Mo., 29. Aug. 2022 um 14:01 Uhr schrieb Mantas Mikulėnas : > > On Mon, Aug 29, 2022 at 1:31 PM Henning Moll wrote: >> >> Hi, >> >> back

Re: [systemd-devel] Service output missing from journal?

Am Mo., 4. Juli 2022 um 19:36 Uhr schrieb Lennart Poettering : > > eOn So, 03.07.22 19:29, Uwe Geuder (systemd-devel-ugeu...@snkmail.com) wrote: > > > Hi! > > > > When I run the command given below on a current Fedora CoreOS system > > (systemd 250 (v250.6-1.fc36)) I get a result I absolute cannot

Re: [systemd-devel] Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora

Am Mo., 2. Mai 2022 um 11:26 Uhr schrieb Lennart Poettering : > > On Sa, 30.04.22 14:54, Andrea Pappacoda (and...@pappacoda.it) wrote: > > > > > If current bootloader already works on platforms supported by > > > > distribution, what is gained by adding yet another one? > > > Freedom of choice > >

Re: [systemd-devel] Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora

Am Mi., 27. Apr. 2022 um 18:02 Uhr schrieb Michael Biebl : > > Am Mi., 27. Apr. 2022 um 17:16 Uhr schrieb Dan Nicholson : > > > > On Wed, Apr 27, 2022 at 9:01 AM Michael Biebl wrote: > > > > > > Slightly related > > > https://salsa.debian.org/system

Re: [systemd-devel] Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora

Am Mi., 27. Apr. 2022 um 17:16 Uhr schrieb Dan Nicholson : > > On Wed, Apr 27, 2022 at 9:01 AM Michael Biebl wrote: > > > > Slightly related > > https://salsa.debian.org/systemd-team/systemd/-/merge_requests/138 > > [sd-boot split] > > https://s

Re: [systemd-devel] Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora

Slightly related https://salsa.debian.org/systemd-team/systemd/-/merge_requests/138 [sd-boot split] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/132 [Draft: Prepare for EFI signing] Am Mi., 27. Apr. 2022 um 16:13 Uhr schrieb Zbigniew Jędrzejewski-Szmek : > > On Wed, Apr 27, 2022

Re: [systemd-devel] Dropping split-usr/unmerged-usr support

Am Di., 5. Apr. 2022 um 22:07 Uhr schrieb Luca Boccassi : > > Hi, > > As part of our spring cleaning effort, we are considering when to drop > support for split/unmerged-usr filesystem layouts. > > A build-time warning was added last year: > >

Re: [systemd-devel] version bump of minimal kernel version supported by systemd?

As far as Debian is concerned, we do have 4.9.x in old old stable aka stretch 4.19.x in old stable aka buster 5.10.x in stable aka bullseye 5.16.x in unstable/bookworm We do provide backports of current systemd versions for bullseye. I also do care that users upgrading from bullseye to bookworm

Re: [systemd-devel] version bump of minimal kernel version supported by systemd?

Am Mi., 23. März 2022 um 22:11 Uhr schrieb Zbigniew Jędrzejewski-Szmek : > Or in other words: I'd prefer for such people to speak up for > themselves, rather than us trying to figure out what somebody else > *might* be planning to do. That's laudable but keep in mind that users typically don't

Re: [systemd-devel] making firewalld an early boot service

Am Mi., 9. März 2022 um 06:49 Uhr schrieb Andrei Borzenkov : > > On 09.03.2022 00:59, Michael Biebl wrote: > > Hi, > > > > I need help with firewalld issue, specifically > > https://github.com/firewalld/firewalld/issues/414 > > > > the TLDR: both firewalld

[systemd-devel] making firewalld an early boot service

Hi, I need help with firewalld issue, specifically https://github.com/firewalld/firewalld/issues/414 the TLDR: both firewalld.service and cloud-init-local.service hook into network-pre.target and have a Before=network-pre.target ordering. cloud-init-local.service is an early boot service using

Re: [systemd-devel] Passive vs Active targets

Fwiw, the Debian rsyslog package does not have any such dependencies/orderings. But there is https://github.com/rsyslog/rsyslog-pkg-rhel-centos/issues/72

Re: [systemd-devel] Antw: [EXT] Service activation

Am Mo., 14. Feb. 2022 um 09:42 Uhr schrieb Wols Lists : > I doubt it. Documentation is excellent at reminding you what you already > knew. It's piss poor at getting a newbie started. The existing documentation of systemd is extensive and well written but indeed probably not very well suited to

Re: [systemd-devel] Service activation

Am So., 13. Feb. 2022 um 17:01 Uhr schrieb Wols Lists : > > On 13/02/2022 15:46, Mantas Mikulėnas wrote: > > On Sun, Feb 13, 2022 at 1:09 PM Wols Lists > > wrote: > > > > On 13/02/2022 09:54, Mantas Mikulėnas wrote: > > > On Sun, Feb 13, 2022 at 2:03 AM

Re: [systemd-devel] eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists

Am Do., 6. Jan. 2022 um 10:00 Uhr schrieb Mantas Mikulėnas : > Grep your entire /etc for those interface names (starting with /etc/udev), > find out where they're defined, and remove them Please also make sure to rebuild your initramfs after doing that. Files from /etc/udev are usually embedded

Re: [systemd-devel] eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists

Am Mi., 5. Jan. 2022 um 13:50 Uhr schrieb Mantas Mikulėnas : > It does, yes, but note this part: > > Jan 03 11:30:14 nasl002b.example.com kernel: igb :02:00.2 eth4: renamed > from eth2 > Jan 03 11:30:14 nasl002b.example.com kernel: igb :02:00.3 eth5: renamed > from eth3 > > Here the

Re: [systemd-devel] [RFC] Switching to OpenSSL 3?

For some reason I sent this message to Lennart only back then, which wasn't my intention. Re-sending it to the mailing list. Am Do., 16. Sept. 2021 um 19:25 Uhr schrieb Michael Biebl : > > Hi Lennart, hi everyone! > > First, a couple of remarks regarding the Debian package: >

Re: [systemd-devel] [EXT] Re: Output from `tee' is not showing up in system journal consistently on some systems

Might be another instance of https://github.com/systemd/systemd/issues/2913 You can verify by checking your whole journal, not just "-u tee_test.service". Am Do., 28. Okt. 2021 um 21:54 Uhr schrieb Mitchel Humpherys : > > On Thu, Oct 28, 2021 at 12:35 AM Ulrich Windl > wrote: > > > > ANother

Re: [systemd-devel] Xorg or Wayland Environment

Just curious: Can someone familiar with KDE/Plasma tell us, if they nowadays (can) use "systemd --user" to manage a login session. Am Di., 21. Sept. 2021 um 12:52 Uhr schrieb Ed Greshko : > > On 21/09/2021 18:20, Colin Guthrie wrote: > > Ed Greshko wrote on 19/09/2021 12:11: > >> OK.. > >>

Re: [systemd-devel] Xorg or Wayland Environment

Am So., 19. Sept. 2021 um 15:48 Uhr schrieb Ed Greshko : > > On 19/09/2021 21:39, Michael Biebl wrote: > > A useful command in this context is > > systemctl --user show-environment > > > OK, that was helpful. But leads to another question. > > How to run the serv

Re: [systemd-devel] Xorg or Wayland Environment

A useful command in this context is systemctl --user show-environment Am So., 19. Sept. 2021 um 11:53 Uhr schrieb Mantas Mikulėnas : > > On Sun, Sep 19, 2021 at 4:05 AM Ed Greshko wrote: >> >> Not a everyday systemd service writer >> >> I've written a user service file to start an app on

Re: [systemd-devel] Xorg or Wayland Environment

You don't hard-code it, you just use it? In your case, since you have a user service which appears bound to the lifetime of a graphical (X/Wayland) session, I guess graphical-session.target is what you want. See man systemd.special. So far, I think only GNOME implements graphical-session.target

Re: [systemd-devel] [hostnamed] Why the service will automatically exit after 30 seconds

Am Mi., 18. Aug. 2021 um 03:35 Uhr schrieb 李成刚 : > > How to configure this service so that it will not automatically exit You can't. The exit-on-idle timeout of 30s is hard-coded.

Re: [systemd-devel] Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

How exactly do you rename your interfaces? Do you use a udev rule? Can you post those scripts/rules?

Re: [systemd-devel] Resource ( systemd )

There is no such property in .service units. What you might do is have .path unit which monitors your python script and triggers a restart.service which restarts server.service Am Mi., 14. Juli 2021 um 04:38 Uhr schrieb Webstrucs : > > I'm developing a web server in python that is referenced in

Re: [systemd-devel] Adding USB ID to hwdb/usb.ids

Am Di., 1. Juni 2021 um 20:44 Uhr schrieb Greg KH : > Works for me! Make sure you are not trying to connect to 'https'. No https? Why? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] minimum required meson version bump?

Am Do., 13. Mai 2021 um 19:15 Uhr schrieb Zbigniew Jędrzejewski-Szmek : > > Hi, > we're considering bumping the meson version from the current 0.46 to > something more recent (0.52 or 0.53…). Ubuntu Biionic 18.04 has 0.45, so > it is below the cutoff point already. Focal 20.04 has 0.53.2. > Would

Re: [systemd-devel] early mounts in systemd

Am Sa., 1. Mai 2021 um 18:07 Uhr schrieb Michael Biebl : > > Am Sa., 1. Mai 2021 um 17:46 Uhr schrieb Dave Howorth > : > > If systemd removes (i.e. doesn't obey) a directive, I'd expect it to be > > polite and log that fact somewhere. No? > > It should, yes. T

Re: [systemd-devel] early mounts in systemd

Am Sa., 1. Mai 2021 um 17:46 Uhr schrieb Dave Howorth : > If systemd removes (i.e. doesn't obey) a directive, I'd expect it to be > polite and log that fact somewhere. No? It should, yes. ___ systemd-devel mailing list

Re: [systemd-devel] early mounts in systemd

Am Sa., 1. Mai 2021 um 08:44 Uhr schrieb Luca Boccassi : > > On Fri, 30 Apr 2021 at 22:15, Michael Biebl wrote: > > > > I wonder if you have a dependency loop somewhere and systemd resolves > > this by removing that ordering. > > As mentioned earlier, I str

Re: [systemd-devel] early mounts in systemd

Am Fr., 30. Apr. 2021 um 20:27 Uhr schrieb Rick Winscot : > At this point, flush is attempting to re-route /run/log/journal to > /var/log/journal ... and the /var partition is not yet mounted. Units > generated for fstab in /run/systemd/generator that manage the mount have an >

Re: [systemd-devel] early mounts in systemd

Am Fr., 30. Apr. 2021 um 19:42 Uhr schrieb Rick Winscot : > > systemd 247 Ok, thanks > /etc/systemd/journald.conf storage is persistent, > systemd-journal-flush.service has RequiresMountsFor=/var/log/journal. > > Mounting /var on a separate read-write partition handles the persistent log >

Re: [systemd-devel] early mounts in systemd

What is the actual problem you have with a separate /var and systemd-journald? For completeness sake, which systemd version do you have? Am Fr., 30. Apr. 2021 um 16:39 Uhr schrieb Rick Winscot : > > We have an embedded product that uses a minimal Linux distribution generated > via Buildroot. > >

Re: [systemd-devel] bitcoind.service activation problem

I guess it's ok to ask such question on this mailing list, as it is rather low traffic. That said, more details are always better. So instead of a screenshot, include a full copy of the service files and the full status and/or journalctl -u bitcoind.service output. This is either a configuration

Re: [systemd-devel] is such a 'failed' state?

Am So., 28. März 2021 um 21:19 Uhr schrieb lejeczek : > Main PID: 922 (code=exited, status=0/SUCCESS) [..] > Restart=on-failure The service terminated with a zero exit code and you use Restart=on-failure. A zero exit code is not treated as failure.

Re: [systemd-devel] Is LTO worth it?

Am Mo., 11. Jan. 2021 um 18:26 Uhr schrieb Reindl Harald : > Am 11.01.21 um 18:10 schrieb Michael Biebl: > > Am Mo., 11. Jan. 2021 um 18:07 Uhr schrieb Reindl Harald > > : > >> it don't make sense using different flags in CI and production builds, > >> espe

Re: [systemd-devel] Is LTO worth it?

Am Mo., 11. Jan. 2021 um 18:10 Uhr schrieb Michael Biebl : > > Am Mo., 11. Jan. 2021 um 18:07 Uhr schrieb Reindl Harald > : > > it don't make sense using different flags in CI and production builds, > > especially LTO which often points out otherwise unvisible bugs > >

Re: [systemd-devel] Is LTO worth it?

Am Mo., 11. Jan. 2021 um 18:07 Uhr schrieb Reindl Harald : > it don't make sense using different flags in CI and production builds, > especially LTO which often points out otherwise unvisible bugs Such as? I don't remember any bug report which was uncovered by LTO being enabled.

Re: [systemd-devel] Is LTO worth it?

Am Mo., 11. Jan. 2021 um 16:39 Uhr schrieb Lennart Poettering : > https://fedoraproject.org/wiki/LTOByDefault Interestingly, that wiki page says, that LTO should produce smaller binaries, which clearly isn't the case here. I wonder whether the wiki is incorrect or whether this is a toolchain

Re: [systemd-devel] Is LTO worth it?

Am Mo., 11. Jan. 2021 um 16:12 Uhr schrieb Reindl Harald : > export LDFLAGS="-Wl,--as-needed -Wl,-z,now -Wl,-z,relro -pie %{optflags} > -flto=%(nproc)" > %meson Thanks for the hint. I tried it, but it didn't really help. ___ systemd-devel mailing list

Re: [systemd-devel] Is LTO worth it?

Am Mo., 11. Jan. 2021 um 15:42 Uhr schrieb Reindl Harald : > it shouldn't if properly used - means param with cpu-cores, just -flto > alone is terrible slow > > -flto=%(nproc) > %{__make} %{?_smp_mflags} The package uses meson's -Db_lto=true ___

[systemd-devel] Is LTO worth it?

Hi, we've been using LTO in the Debian build for as long as I can remember, but I begin to question whether that is a good idea. On Debian sid (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1), an LTO build almost takes twice as long as a no-LTO build. I also

Re: [systemd-devel] SystemD dependency problem

In addition to what Mantas said, I'd suggest reading man systemd.special. and https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ This should give you an idea what network-online.target is supposed to be. It's not a target to hook arbitrary services into (via WantedBy). Your service

Re: [systemd-devel] Help with Systemd + Apache 2.4 - CentOS 7

Am Mo., 23. Nov. 2020 um 02:33 Uhr schrieb Lucas Possamai : > > Hi, > > I have Apache 2.4.6-93 running on a CentOS 7.8.2003 that is not starting > using Systemd. > > If I do: systemctl start httpd, I get the following error: > > Nov 22 20:14:11 localhost systemd[1]: Failed to start The Apache

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

Am Do., 12. Nov. 2020 um 18:13 Uhr schrieb Zbigniew Jędrzejewski-Szmek : > The tags change is probably limited in effect, and the lack of handling > of "bind" in rules will be more important. But, as you said, that change > was already happening since kernel 4.2. So it's possible that the biggest

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

Hi there Am Do., 12. Nov. 2020 um 11:58 Uhr schrieb systemd tag bot : > > A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the > tarball here: > > https://github.com/systemd/systemd/archive/v247-rc2.tar.gz Congrats to the new release! > Changes since the previous

Re: [systemd-devel] ssh.service in rescue.target

Am Mo., 9. Nov. 2020 um 18:25 Uhr schrieb Michael Biebl : > I guess this is kinda moot now, given that the initscripts package was > completely removed in Ubuntu 20.10 it seems. > Fwiw, I'd be surprised if there really are any packages in 20.04 still > depending on initscripts. > M

Re: [systemd-devel] ssh.service in rescue.target

Am Mo., 9. Nov. 2020 um 18:20 Uhr schrieb Michael Biebl : > > Am Mo., 9. Nov. 2020 um 17:12 Uhr schrieb Simon McVittie : > > > > On Mon, 09 Nov 2020 at 09:16:05 -0500, Phillip Susi wrote: > > > I guess I'll try masking it. > > > > The Debian/Ubuntu pa

Re: [systemd-devel] ssh.service in rescue.target

Am Mo., 9. Nov. 2020 um 17:12 Uhr schrieb Simon McVittie : > > On Mon, 09 Nov 2020 at 09:16:05 -0500, Phillip Susi wrote: > > I guess I'll try masking it. > > The Debian/Ubuntu package for systemd already masks various services > that are superseded by something in systemd, such as procps.service

Re: [systemd-devel] ssh.service in rescue.target

Am Fr., 6. Nov. 2020 um 22:31 Uhr schrieb Phillip Susi : > > > Lennart Poettering writes: > > > Are you running systemd? If so, please get rid of "killproc". It will > > interfere with systemd's service management. > > I see.. apparently Ubuntu still has it around. Are you sure? Which Ubuntu

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

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???

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

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

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"

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?

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

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

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

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?

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

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

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

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

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

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

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'

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

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

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)

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)

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

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

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

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?

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?

[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?

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?

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)

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

  1   2   3   4   5   6   7   >