On Wed, Dec 15, 2021 at 09:37:41PM -0500, Tim Safe wrote:
> Hello-
>
> I have an Ubuntu Server 20.04 (systemd 245 (245.4-4ubuntu3.13)) box that I
> recently installed a Intel quad-port Gigabit ethernet adapter (E1G44ETBLK).
>
> It appears that the predictable interface naming is only renaming the
On Thu, Dec 16, 2021 at 07:27:44AM -0500, Tim Safe wrote:
> Thanks for the reply! Here's the output:
>
> $ udevadm test-builtin net_id /sys/class/net/ens8f0
> ID_NET_NAME_SLOT=ens8f0
>
> $ udevadm test-builtin net_id /sys/class/net/ens8f1
> ID_NET_NAME_SLOT=ens8f1
>
> $ udevadm test-builtin net_
As Lennart wrote, some of the changes since v245 are likely to fix
your issue. I'd put my money on
https://github.com/systemd/systemd/commit/2c8ec0095e i.e. systemd 247,
but it's probably best to try systemd 249.
Zbyszek
On Mon, Jan 10, 2022 at 12:15:22PM +0100, Ulrich Windl wrote:
> >>> "Manuel Wagesreither" schrieb am 10.01.2022 um 11:43
> >>> in
> Nachricht <759bd805-ab37-4dc9-93cd-137668acf...@www.fastmail.com>:
> > Hi all,
> >
> > currently, the systemd.mount man page [1] claims that "In general,
> > confi
Hi all,
we are considering dropping upstream support for kernel versions < 4.4.
Would this be a problem for anyone? (*).
Zbyszek
(*) If you answer "yes", please substantiate why you are running new
systemd with such old kernels.
On Wed, Mar 23, 2022 at 08:07:48AM +0100, Greg KH wrote:
> On Tue, Mar 22, 2022 at 05:27:07PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > Hi all,
> >
> > we are considering dropping upstream support for kernel versions < 4.4.
> > Would this be a problem for anyone?
On Wed, Mar 23, 2022 at 09:26:05AM +0100, Greg KH wrote:
> On Wed, Mar 23, 2022 at 09:17:36AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > On Wed, Mar 23, 2022 at 08:07:48AM +0100, Greg KH wrote:
> > > On Tue, Mar 22, 2022 at 05:27:07PM +0100, Zbigniew Jędrzejewski-Szmek
>
On Wed, Mar 23, 2022 at 03:58:22PM +, Luca Boccassi wrote:
> On Wed, 2022-03-23 at 12:38 +0100, Greg KH wrote:
> > On Wed, Mar 23, 2022 at 11:28:29AM +, Luca Boccassi wrote:
> > > On Wed, 2022-03-23 at 11:59 +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > > >
On Thu, Mar 24, 2022 at 08:21:37AM +0100, Ulrich Windl wrote:
> I wonder:
>
> Why not providing some test suite instead: If the test suite succeeds, systemd
> might work; if it doesn't, manual steps are needed.
> My guess is that most people will quit trying once manual steps are needed.
> In addi
On Thu, Mar 24, 2022 at 08:08:31AM +0100, Greg KH wrote:
> On Wed, Mar 23, 2022 at 10:11:36PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> >
> > CIP 4.4 is supposed to be maintained until 2027, which is awfully
> > long. The question is: is anyone putting new systemd on thos
On Thu, Mar 24, 2022 at 10:28:39AM +, Luca Boccassi wrote:
> On Thu, 2022-03-24 at 09:38 +0100, Lennart Poettering wrote:
> > On Mi, 23.03.22 11:28, Luca Boccassi (bl...@debian.org) wrote:
> >
> > > At least according to our documentation it wouldn't save us much
> > > anyway, as the biggest le
On Thu, Apr 07, 2022 at 04:37:48PM +0530, Nikhil Kshirsagar wrote:
> Is there any chance systemd could support a configuration option in the
> future to get the earlier "all numeric" user logins to work? With an
> understanding that it would be at the users own risk?
No.
> Are there any pam_system
On Tue, Apr 26, 2022 at 07:12:02PM -0400, Neal Gompa wrote:
> Hey all,
Hi Neal,
thank you for starting the discussion. I think it'd be good to figure
out what are the high-level options we have as a community…
> Some of you might know about the recent discussion in Fedora about
> dropping BIOS s
On Wed, Apr 27, 2022 at 08:55:55AM -0400, Neal Gompa wrote:
> On Wed, Apr 27, 2022 at 6:47 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Tue, Apr 26, 2022 at 07:12:02PM -0400, Neal Gompa wrote:
> > > Hey all,
> >
> > Hi Neal,
> >
> > tha
On Wed, Apr 27, 2022 at 09:31:10AM -0400, Neal Gompa wrote:
> On Wed, Apr 27, 2022 at 7:41 AM Lennart Poettering
> wrote:
> It is not very friendly when you're in a failure scenario or have to
> deal with boot stuff.
Well, if you have a boot failure, then a text-based interface is better
than a g
On Wed, Apr 27, 2022 at 11:26:14AM -0400, Neal Gompa wrote:
> On Wed, Apr 27, 2022 at 11:13 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Wed, Apr 27, 2022 at 09:31:10AM -0400, Neal Gompa wrote:
> > > On Wed, Apr 27, 2022 at 7:41 AM Lennart Poettering
> &g
On Wed, Apr 27, 2022 at 11:48:04AM -0400, Neal Gompa wrote:
> On Wed, Apr 27, 2022 at 11:46 AM Luca Boccassi wrote:
> >
> > On Wed, 2022-04-27 at 11:26 -0400, Neal Gompa wrote:
> > > On Wed, Apr 27, 2022 at 11:13 AM Zbigniew Jędrzejewski-Szmek
> > > wrote:
> &
On Wed, Apr 27, 2022 at 11:40:36AM -0400, Neal Gompa wrote:
> On Wed, Apr 27, 2022 at 11:26 AM Dan Nicholson wrote:
> >
> > On Wed, Apr 27, 2022 at 9:10 AM Neal Gompa wrote:
> > >
> > > Note that it means Fedora CI, pull requests from contributors, and
> > > releng auto-rebuilds will no longer wo
On Mon, May 09, 2022 at 03:57:21PM +0200, Lennart Poettering wrote:
> On Mo, 09.05.22 11:23, Thomas Haller (thal...@redhat.com) wrote:
>
> > Hi everybody,
> >
> > this email is for discussing MACAddressPolicy=persistent in
> > /data/src/systemd/network/99-default.link
>
> I think this would be be
On Thu, May 19, 2022 at 01:42:43PM +0200, Daan De Meyer wrote:
> > Am 19.05.22 um 05:32 schrieb Dusty Mabe:
> > > I'm requesting help to try to find a problematic commit between
> > > v251-rc2..v251-rc3.
> > >
> > > We have a test in Fedora CoreOS [1] that tests luks and this test
> > > started fai
On Fri, May 20, 2022 at 03:51:58PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, May 19, 2022 at 01:42:43PM +0200, Daan De Meyer wrote:
> > > Am 19.05.22 um 05:32 schrieb Dusty Mabe:
> > > > I'm requesting help to try to find a problematic commit betwe
On Mon, May 23, 2022 at 01:24:44PM +, Dave Glenton wrote:
> Sorry if this question is covered elsewhere, but a couple of days of googling
> and experimentation has failed to find a solution and hopefully someone in
> this list can give me some pointers.
>
> I am trying to configure an Open E
[I misplaced the original mail, so I'm replying to a forward.
Apologies if threading is broken.]
> What do we propose to do?
> -
>
> We want to bring pystemd[1] into the systemd organization, and merge
> (functionality wise) with python-systemd[2], so that there is a single
> Python library,
On Thu, Dec 22, 2022 at 08:00:06PM +1100, Michael Chapman wrote:
> On Thu, 22 Dec 2022, Andrei Borzenkov wrote:
> > On Thu, Dec 22, 2022 at 11:17 AM Nicolas Pillot
> > wrote:
> > >
> > > Hello
> > >
> > > I am wondering if i can dynamically plan jobs (once) using systemd timer.
> > > What i mean
On Mon, Mar 20, 2023 at 01:50:02PM -0400, Znoteer wrote:
> Hi,
>
> I've tried twice sending an email to systemd-devel-request@l.f.o with
> unsubscribe in the subject and then in the body. Thoese mails were both
> rejected.
>
> I tried also subscribing via the maillist web site form. That also
On Mon, May 15, 2023 at 10:21:27PM +, Dave Re wrote:
>
> Hi, all,
>
> Hoping to get some assistance root causing this issue. We have a set of
> CentOS 7 based systems in AWS that we're using the leapp tool to migrate to
> AlmaLinux 8.7. Following migration, the root filesystem is ending up
On Tue, May 16, 2023 at 02:37:58PM +, Dave Re wrote:
>
> Hi, Zbyszek,
>
> The kernel default is to mount root ro, so unless there's some configuration
> to
> mount or remount it rw, it'll stay ro. Generally this is configured in two
> places 'rw' on the kernel command line and 'rw' in /etc/f
On Tue, May 16, 2023 at 05:26:00PM +, Dave Re wrote:
> One step I haven't taken is turning on debug level logging in systemd - not
> sure what to expect (or not expect) out of it, but I guess that's my next
> step. I'd welcome any pointers to debugging resources, etc, but realize this
> is a
Hi,
I'd like to start $subject. First, we'd just add an entry in NEWS
and make the key generation code print a warning, but then in a release
or few remove the code.
See https://github.com/systemd/systemd/pull/28433/commits/1ecd1a994733d.
If you're using FSS, please speak up.
Zbyszek
On Wed, Jul 26, 2023 at 03:23:14AM +, Muggeridge, Matt wrote:
> Hi,
>
> Recently, we ran a test suite to check networkd's conformance to IPv6
> Protocol (see https://www.ipv6ready.org/resources.html). I found a large
> number of test failures (more than 80) and after examining a small numbe
On Mon, Sep 18, 2023 at 04:17:49PM +0200, Lennart Poettering wrote:
> On Mo, 18.09.23 15:22, mpan (systemdml-bfok4...@mpan.pl) wrote:
>
> > Hello,
> >
> > I got redirected to here from #systemd on Libera. While responding to a
> > query from another person (not on #systemd), I came across an amb
On Thu, Nov 23, 2023 at 02:33:55PM +0800, d tbsky wrote:
> Hi:
>I saw systemd 252 release notes:
>
> Private shared libraries (libsystemd-shared-nnn.so,
> libsystemd-core-nnn.so) are now installed into arch-specific
> directories to allow multi-arch installs.
>
> I don't know if that is rel
On Tue, Jan 15, 2019 at 01:09:16PM +0100, Lennart Poettering wrote:
> On Mo, 14.01.19 11:26, Dave Reisner (d...@falconindy.com) wrote:
> > >
> > > Well, that sounds as if you want to volunteer as release engineer? ;-)
> > >
> > > Thing is, we are understaffed. I too have a wishlist of things I'd
>
Hi everyone,
241 will be released soon. Current list of outstanding tickets [1]:
"23 wireguard peers hang systemd-networkd"
#11404 opened 3 days ago by darkk
network: wait for kernel to reply ipv6 peer address
#11428
(needs review)
"Bump numbers for v241"
#11387
(release mechanics)
"Add 'udevad
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, Michael Biebl (mbi...@gmail.com) wrote:
> >
> > > Looks like quite a few services use
> > > WantedBy=default.target
> > > https://codesear
On Mon, Mar 25, 2019 at 10:18:06PM +0100, Reindl Harald wrote:
>
>
> Am 25.03.19 um 22:00 schrieb Belisko Marek:
> > in my app I need to delay startup until network is really up & running.
> > I go through [1] and it mentions that it works only with NetworkManager
> > and systemd-networkd. I'm us
On Wed, Apr 03, 2019 at 07:55:42AM +, systemd tag bot wrote:
> A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the
> tarball here:
Please ignore this one. The version number was not bumped properly.
v242-rc2 has already been tagged.
Zbyszek
_
On Mon, Apr 29, 2019 at 09:22:30PM +0200, linuxfr...@gmx.at wrote:
> Hi,
>
> i do not know who is the correct person / mailing list, to ask for this one.
>
> 1) screen-lock locks the screen (OK)
>
> 2) screensaver comes and screen is going to be black. (OK)
>
> 3) Everytime i unlock my locked
On Mon, Apr 29, 2019 at 09:32:57PM +0200, linuxfr...@gmx.at wrote:
> Hi Zbyszek,
>
>
> i've already did this.
>
> It started after desktop freezes here:
>
> https://forum.manjaro.org/t/xfce-desktop-freezes-after-automated-screen-lock-manjaro-18-0-4-illyria/84717/12
>
> which were solved, but t
On Fri, May 10, 2019 at 09:27:17AM -0600, Roger Pack wrote:
> Hello, I'm trying to answer this question:
>
> https://unix.stackexchange.com/questions/517872/systemctl-list-all-possible-including-disabled-services
>
> Basically, I have a my_service.service that is disabled, I wish I
> could "see t
On Thu, May 16, 2019 at 12:04:28PM +0200, Ulrich Windl wrote:
> >>> Lennart Poettering schrieb am 16.05.2019 um 10:29
> in
> Nachricht <20190516082910.GA24042@gardel-login>:
> > On Do, 16.05.19 08:55, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
> wrote:
> >
> >> Hi!
> >>
> >> After having re
On Mon, May 20, 2019 at 03:36:28PM +0200, Ulrich Windl wrote:
> Hi!
>
> I have had the effect that a "systectl status" before and after a
> "daemon-reload" is different, while the service in question wasn't restarted:
Whenever making a report like this, always include the exact systemd
version yo
On Thu, May 23, 2019 at 09:25:02AM +0100, Rory Bradford wrote:
> Hi,
>
> I actively maintain a Node.js module "sd-notify" available on GitHub
> (https://github.com/roryrjb/sd-notify) and npm
> (https://www.npmjs.com/package/sd-notify) that has been contributed to
> and is being used by others. As
n 23/05/2019 10:04, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, May 23, 2019 at 09:25:02AM +0100, Rory Bradford wrote:
> >> Hi,
> >>
> >> I actively maintain a Node.js module "sd-notify" available on GitHub
> >> (https://github.com/roryrjb/sd-
; On Thu, May 23, 2019 at 12:05 PM Zbigniew Jędrzejewski-Szmek
> > mailto:zbys...@in.waw.pl>> wrote:
> >
> > On Thu, May 23, 2019 at 09:25:02AM +0100, Rory Bradford wrote:
> > > Hi,
> > >
> > > I actively maintain a Node.js m
On Thu, May 23, 2019 at 12:43:27PM +0100, Rory Bradford wrote:
> Yup, go for it.
Done.
Zbyszek
> On 23/05/2019 12:36, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, May 23, 2019 at 12:27:56PM +0100, Rory Bradford wrote:
> >> Yeah of course, didn't even think. I'
On Tue, May 28, 2019 at 12:59:27PM +0200, Wiktor Kwapisiewicz wrote:
> Hello,
>
> I've enabled "RuntimeWatchdogSec=30" in /etc/systemd/system.conf
> (after reading excellent "systemd for Administrators" series [0]).
>
> Before enabling that "wdctl" printed nice statistics but now it only
> inform
On Tue, May 28, 2019 at 01:50:53PM +0200, Wiktor Kwapisiewicz wrote:
> Hi Zbyszek,
>
> On 28.05.2019 13:43, Zbigniew Jędrzejewski-Szmek wrote:
> >What kind of information are you after?
>
> One interesting statistic I'd like to see changing is the time when
> t
On Tue, Jun 04, 2019 at 12:42:35PM -0400, Steve Dickson wrote:
> Hello,
>
> We are adding some new functionality to the NFS server that
> will make it a bit more container friendly...
>
> This new functionality needs to do a chroot(2) system call.
> This systemcall is failing with EPERM due to
On Fri, Jun 07, 2019 at 03:48:58AM +, 程 书意 wrote:
> Hi all,
>
> I am working on virtualization on armv8 platform and encountered a complex
> problem. From the below boot log, we can find:
>
> 1. Every unit init need about 30 seconds.
> 2. status_printf function doesn't work. [no status
On Sun, Jun 09, 2019 at 05:58:16PM -0300, Leonardo Akel Daher wrote:
> Hi,
>
> I am trying to make a Pull Request for systemd, but I am struggling running
> the tests locally (before making any code changes). I get the error of the
> attached image when running "ninja -C build/ test".
Hi,
please
On Mon, Jun 24, 2019 at 02:11:03PM +0200, Lennart Poettering wrote:
> On Sa, 22.06.19 10:42, Chris Murphy (li...@colorremedies.com) wrote:
>
> > Hi,
> >
> > I've got a commit to add 'Conflicts=umount.target' to this zram
> > service based on a bug comment I cited in the comment. But I'm not
> > ce
On Tue, Jun 25, 2019 at 10:55:27AM +0200, Lennart Poettering wrote:
> On Mo, 24.06.19 13:16, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > > So for tmpfs mounts that don't turn off DefaultDependencies= we
> > > implicit add in an After=swap.target o
On Tue, Jul 02, 2019 at 03:39:04PM +0200, ABDUL MAJITH wrote:
> Hi all,
>
> I am trying to use the Docker in GNS3, when I try to launch it show the
> error as follows,
>
> -- The start-up result is done.
> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request
> repeated too qu
On Tue, Jul 09, 2019 at 08:49:32AM +0200, Ulrich Windl wrote:
> Hi!
>
> It seems "--state=failed" is being ignored silently for "systemctl status"
> (in version 228). Is this by design?
Nope. In 242-1092+ it seems to work fine.
Zbyszek
___
systemd-dev
On Tue, Jul 09, 2019 at 10:23:47AM +0200, Ulrich Windl wrote:
> >>> Zbigniew Jedrzejewski-Szmek schrieb am 09.07.2019 um
> 10:05
> in Nachricht <20190709080527.gk17...@in.waw.pl>:
> > On Tue, Jul 09, 2019 at 08:49:32AM +0200, Ulrich Windl wrote:
> >> Hi!
> >>
> >> It seems "‑‑state=failed" is bei
On Tue, Jul 02, 2019 at 09:57:44AM -0400, Brian Reichert wrote:
> At $JOB, on some of our SLES12 boxes, our logs are getting swamped
> with messages saying:
>
> "Too many concurrent connections, refusing"
Please always specify the systemd version in use. We're not all SLES
users, and even if we
On Tue, Jul 09, 2019 at 11:05:50PM +0300, Mantas Mikulėnas wrote:
> On Tue, Jul 9, 2019 at 4:28 PM Brian Reichert wrote:
>
> > On Tue, Jul 09, 2019 at 11:21:13AM +0100,
> > systemd-devel@lists.freedesktop.org wrote:
> > > Hi Brian
> > >
> > > I feel embarrassed at having recommended you to join t
On Wed, Jul 10, 2019 at 09:51:36AM -0400, Brian Reichert wrote:
> On Wed, Jul 10, 2019 at 07:37:19AM +, Zbigniew J??drzejewski-Szmek wrote:
>
> > It's a bug report as any other. Writing a meaningful reply takes time
> > and effort. Lack of time is a much better explanation than ressentiments.
On Thu, Jul 11, 2019 at 10:08:43AM -0400, Brian Reichert wrote:
> On Wed, Jul 10, 2019 at 10:44:14PM +, Zbigniew J??drzejewski-Szmek wrote:
> > That's ancient... 228 was released almost four years ago.
>
> That's the joy of using a commercial Linux distribution; they tend
> to be conservative
On Thu, Jul 18, 2019 at 11:46:59AM +0300, Mantas Mikulėnas wrote:
> On Thu, Jul 18, 2019 at 11:34 AM Ulrich Windl <
> ulrich.wi...@rz.uni-regensburg.de> wrote:
>
> > Hi!
> >
> > I noticed that a line of "===" in "[Service]" cases the message "
> > Unknown lvalue '' in section 'Service'".
> > (
On Wed, Jul 24, 2019 at 03:48:40PM +0200, Francis Moreau wrote:
> Hi,
>
> I would like to backup the journal logs for the current boot in a
> "raw" format so I can reuse it later with "journalctl
> --file=my-backup".
>
> But looking at the different values for "-o" option I can't find the answer.
On Tue, Jul 30, 2019 at 08:32:44AM +1000, Clinton Roy wrote:
> Particularly the following sentence:
>
> This option defaults to off, since it depends on drivers and
> software setup whether the watchdog is correctly reset again after
> the kexec completed, and thus for the general case not clear i
On Thu, Aug 01, 2019 at 09:11:19AM +0200, Francis Moreau wrote:
> On Wed, Jul 24, 2019 at 4:08 PM Zbigniew Jędrzejewski-Szmek
> wrote:
> > you can export and write to a journal file with:
> > journalctl -o export ... | /usr/lib/systemd/systemd-journal-remote -o
> > /tm
On Wed, Jul 31, 2019 at 11:37:31AM -0400, Brian Reichert wrote:
> On Wed, Jul 31, 2019 at 12:36:41AM +0300, Uoti Urpala wrote:
> > On Tue, 2019-07-30 at 14:56 -0400, Brian Reichert wrote:
> > > I see, between 13:49:30 and 13:50:01, I see 25 'successful' calls
> > > for close(), e.g.:
> > >
> > >
On Thu, Aug 01, 2019 at 10:26:50AM +0200, Francis Moreau wrote:
> On Thu, Aug 1, 2019 at 9:45 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Thu, Aug 01, 2019 at 09:11:19AM +0200, Francis Moreau wrote:
> > > On Wed, Jul 24, 2019 at 4:08 PM Zbigniew Jędrzejewski-Szme
On Thu, Aug 01, 2019 at 10:52:07AM +0200, Francis Moreau wrote:
> On Thu, Aug 1, 2019 at 10:36 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Thu, Aug 01, 2019 at 10:26:50AM +0200, Francis Moreau wrote:
> > > On Thu, Aug 1, 2019 at 9:45 AM Zbigniew Jędr
On Thu, Aug 01, 2019 at 08:46:58AM -0400, Brian Reichert wrote:
> On Thu, Aug 01, 2019 at 08:17:01AM +, Zbigniew J??drzejewski-Szmek wrote:
> > The kernel will use the lower-numbered available fd, so there's lot of
> > "reuse" of the same numbers happening. This strace means that between
> > ea
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 (-Db_lto=false).
>
> The lto build took approximately twice as long on my laptop (using
> dpkg-buildpackage, which int
On Tue, Aug 06, 2019 at 09:34:36AM +0200, Michael Biebl wrote:
> 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 comp
On Sun, Aug 18, 2019 at 05:02:35PM +0100, Steve Dodd wrote:
> ARM has two sync_file_range syscalls, sync_file_range and sync_file_range2.
> The former is apparently not used, and glibc calls the latter whenever a
> userspace program calls sync_file_range. I'm guessing systemd-nspawn
> doesn't know
On Fri, Aug 23, 2019 at 11:43:43AM -0700, Filipe Brandenburger wrote:
> Hi,
>
> I've been trying to get sd-boot to work on Fedora 30, made some progress
> but not fully there yet...
>
> First I found my partition GPT type in /boot was incorrect and bootctl was
> trying to use /boot/efi instead. O
On Fri, Aug 30, 2019 at 04:08:39PM +0200, Hans de Goede wrote:
> Hi All,
>
> I already filed a github issue for $subject:
> https://github.com/systemd/systemd/issues/13437
>
> But I'm not sure how close github issues are watched hence this email. It
> would be nice if we can get this fixed for F3
On Fri, Aug 30, 2019 at 06:04:22PM -0700, Kenneth Porter wrote:
> I've created my service timer with the following:
>
> [Timer]
> # wait a bit after boot to let our victim catch up with its work
> OnBoot=13m
This needs to be OnBootSec=13m. (systemd-analyze verify is your friend
in cases like this
On Mon, Sep 02, 2019 at 07:55:20PM -0600, Chris Murphy wrote:
> Maybe it's something unique to gnome-shell segfaults, that's the only
> thing I have crashing right now. But I've got a pretty good reproducer
> to get it to crash and I never have any listings with coredumpctl.
>
> process segfaults
On Sun, Sep 15, 2019 at 03:12:22AM +, Daniel Duong wrote:
> Hi,
>
> I have a 2 template units: 1 for a service and 1 for a socket. Each
> instance is a version of my web application.
>
> After a successful deploy, I stop and disable the old version and I
> enable the new one:
> systemct
On Sat, Oct 05, 2019 at 09:34:09AM +0200, azu...@pobox.sk wrote:
> Hi guys.
>
> recently, we upgraded one of our servers from Debian Stretch
> (systemd version 232-25+deb9u12) to Debian Buster (systemd version
> 241-7~deb10u1). Soon after, we found out that setting
> 'JoinControllers' is not longe
On Tue, Oct 15, 2019 at 04:08:24PM -0400, Brian Reichert wrote:
> I initiated an unsubscribe from this web page:
>
> https://lists.freedesktop.org/mailman/options/systemd-devel
>
> That created a confirmation email, that I replied to.
Yeah, that doesn't work. Use the web interface:
> https://l
In principle, the watchdog for services is nice. But in practice it seems
be bring only grief. The Fedora bugtracker is full of automated reports of
ABRTs,
and of those that were fired by the watchdog, pretty much 100% are bogus, in
the sense that the machine was resource starved and the watchdog
On Tue, Oct 22, 2019 at 09:54:31AM +0300, Pekka Paalanen wrote:
> On Mon, 21 Oct 2019 17:50:44 +
> Zbigniew Jędrzejewski-Szmek wrote:
>
> > In principle, the watchdog for services is nice. But in practice it seems
> > be bring only grief. The Fedora bugtracker is full of
On Mon, Oct 21, 2019 at 02:32:08PM -0700, Vito Caputo wrote:
> On Mon, Oct 21, 2019 at 05:50:44PM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> > In principle, the watchdog for services is nice. But in practice it seems
> > be bring only grief. The Fedora bugtracker is full of autom
g.
There might be cases where the kernel is dead-locked internally, and e.g.
open() or modprobe() never returns. For those cases it might be useful to
get the backtrace, but actually killing the process and/or storing the
coredump is useful.
Zbyszek
>
> Umut
>
> On Mon, Oct 21,
On Tue, Oct 22, 2019 at 04:35:13AM -0700, Vito Caputo wrote:
> On Tue, Oct 22, 2019 at 10:51:49AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Oct 22, 2019 at 12:34:45PM +0200, Umut Tezduyar Lindskog wrote:
> > > I am curious Zbigniew of how you find out if the coredum
On Thu, Oct 24, 2019 at 02:56:55PM -0700, Vito Caputo wrote:
> On Thu, Oct 24, 2019 at 10:45:32AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Oct 22, 2019 at 04:35:13AM -0700, Vito Caputo wrote:
> > > On Tue, Oct 22, 2019 at 10:51:49AM +, Zbigniew Jędrzejewski-
Hi everyone,
I think it's time to get ready for a v244-prerelease.
Currently, 8 issues are open on
https://github.com/systemd/systemd/milestones/v244
without a PR. I'll be working on the remaining issues and hope to release an
-rc1
late this week or early next.
If there is stuff I should review
On Thu, Oct 31, 2019 at 06:30:33PM +0100, Lennart Poettering wrote:
> On Mo, 21.10.19 17:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > In principle, the watchdog for services is nice. But in practice it seems
> > be bring only grief. The Fedora bugtracker is
On Thu, Nov 07, 2019 at 02:12:55PM +, kein name wrote:
> Hi,
>
> I'd like to report a dead link in the documentation of the Journal File
> Format on freedesktop.org[1].
> The link[2] goes to gmane.org which is dead, it should probably use your own
> mailing list archive[3].
Thanks, updated.
On Mon, Nov 18, 2019 at 11:41:20AM +, Marcos Mello wrote:
> Although util-linux's fstab.d work has stalled, there is still systemd code
> that needs porting to libmount. See Karel's last comment:
>
> https://github.com/systemd/systemd/issues/12506
Reopened.
Zbyszek
_
On Mon, Nov 25, 2019 at 06:13:17PM +0200, Uoti Urpala wrote:
> On Mon, 2019-11-25 at 15:19 +0200, Mantas Mikulėnas wrote:
> > > Requires=xyz.service
> > >
> > > produces no complaint and starts the service even if there is no
> > > xyz.service
> > > Is this the normal behavior or can I configure
On Sat, Dec 14, 2019 at 11:58:37AM +0300, Andrei Borzenkov wrote:
> 09.12.2019 10:06, Ulrich Windl пишет:
> >>
> >> After real root is mounted daemon-reload re-runs fstab generator which
> >> parses real root /etc/fstab and may pull mount points from it.
> >
> > I wonder: Are there realistic cases
On Thu, Jan 02, 2020 at 12:21:26AM +0800, Kairui Song wrote:
> Some component, like Systemd, have grown by a lot, here is a list of
> the size of part of binaries along with the binaries they required in
> F31:
> /root/image/bin/systemctl
> 20M .
> /root/image/usr/bin/systemctl
> 20M .
> /r
On Thu, Jan 02, 2020 at 03:29:26PM -0500, Robbie Harwood wrote:
> Kairui Song writes:
>
> > What I'm trying to do is reduce the initramfs size used for kdump.
> > Kdump loads a crash kernel and kdump initramfs image in a prereseved
> > memory region, which get booted when current kernel crashed a
On Fri, Jan 03, 2020 at 11:48:53AM +0800, Dave Young wrote:
> On 01/03/20 at 11:45am, Dave Young wrote:
> > On 01/02/20 at 09:02am, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Thu, Jan 02, 2020 at 12:21:26AM +0800, Kairui Song wrote:
> > > > Some component, like Syst
Dear all,
we'll be having an open meeting in Brno on Thursday, Jan 23rd, 2020,
before the DevConf.cz conference. Everyone interested in systemd
development is invited. The plan is to meet for lunch around 1 PM, and
then go the Red Hat office afterwards for discussion and planning.
We should be at
, Zbigniew Jędrzejewski-Szmek wrote:
> Dear all,
>
> we'll be having an open meeting in Brno on Thursday, Jan 23rd, 2020,
> before the DevConf.cz conference. Everyone interested in systemd
> development is invited. The plan is to meet for lunch around 1 PM, and
> then go
On Tue, Feb 25, 2020 at 01:12:08PM +0800, Kairui Song wrote:
> On Fri, Jan 3, 2020 at 3:23 PM Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Fri, Jan 03, 2020 at 11:48:53AM +0800, Dave Young wrote:
> > > On 01/03/20 at 11:45am, Dave Young wrote:
> > > > On 01/02/20
On Mon, Mar 02, 2020 at 01:38:54PM +0100, Łukasz Niemier wrote:
> > AFAIK both stdout and stderr even get attached to the same journal pipe by
> > default, so they should also be interpreted in the same way.
> >
> > The description of SyslogLevelPrefix= in systemd.exec(5) also says: "This
> > on
On Tue, Mar 03, 2020 at 07:43:22AM +, systemd tag bot wrote:
> A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the
> tarball here:
>
> https://github.com/systemd/systemd/archive/v245-rc2.tar.gz
It's mostly bufixes, but still 146 commits since -rc1.
The plan is t
On Thu, Mar 26, 2020 at 01:05:22PM -0500, Eric DeVolder wrote:
> >Below is a proposal for adding a couple of settings to the systemd pstore
> >service so that it can enable the kernel parameters that allow the
> >kernel to write into the pstore.
Hi,
please submit this as PR.
> > From 837d716c6e7
On Fri, Apr 10, 2020 at 10:53:36AM -0500, Matt Zagrabelny wrote:
> 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
1 - 100 of 2703 matches
Mail list logo
