[systemd-devel] Wtrlt: Antw: [EXT] Re: Why are core dumps named vgcore.*?

2021-06-15 Thread Ulrich Windl
(Once again forgot the list) >>> Ulrich Windl schrieb am 15.06.2021 um 14:25 in Nachricht <60c8b857.ed38.00a...@rz.uni-regensburg.de>: >>>> Mantas Mikulenas schrieb am 15.06.2021 um 10:45 in > Nachricht > : > > On Tue, Jun 15, 2021 at 9:04 AM Ulrich Windl

[systemd-devel] Why are core dumps named vgcore.*?

2021-06-15 Thread Ulrich Windl
Hi! I'm developing a program that dumps core on some failed assertions. I noticed that the core dumps are created in the user directory as vgcore.. Where does the name vgcore come from? And is it OK to remove just those files, or does coredumpctl store additional infos? Regards, Ulrich

[systemd-devel] Antw: Re: Antw: [EXT] Block systemd from adding new services

2021-06-14 Thread Ulrich Windl
>>> Andy Pieters schrieb am 14.06.2021 um 10:09 in Nachricht : > On Mon, 14 Jun 2021 at 09:05, Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> >> The better solution would have been to pick a stronger password IMHO. >> >> >> O

[systemd-devel] Antw: [EXT] Block systemd from adding new services

2021-06-14 Thread Ulrich Windl
>>> Saint Michael schrieb am 13.06.2021 um 15:32 in >>> Nachricht : > One of the most dramatic hacks to 50+ servers of mine is a bitcoin miner, > xmrig. It installs a service file at /etc/systemd/system, enables it and > kills the machine. > Nobody knows how it propagates. I think that SSHD has

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

2021-06-04 Thread Ulrich Windl
>>> "Ulrich Windl" schrieb am 04.06.2021 um 07:48 in Nachricht <60b9bebf02a100041...@gwsmtp.uni-regensburg.de>: >>>> Greg KH schrieb am 02.06.2021 um 16:39 in > Nachricht : >> On Wed, Jun 02, 2021 at 03:48:41PM +0200, Reindl Harald wrote: >

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

2021-06-03 Thread Ulrich Windl
>>> Greg KH schrieb am 02.06.2021 um 16:39 in Nachricht : > On Wed, Jun 02, 2021 at 03:48:41PM +0200, Reindl Harald wrote: >> >> >> Am 02.06.21 um 07:04 schrieb Greg KH: >> > On Tue, Jun 01, 2021 at 09:38:37PM +0200, Michael Biebl wrote: >> > > Am Di., 1. Juni 2021 um 20:44 Uhr schrieb Greg KH

[systemd-devel] Wtrlt: Re: Antw: [EXT] Re: What causes "systemd-journald[3256]: Missed 127 kernel messages"

2021-06-01 Thread Ulrich Windl
(forgot the list) >>> Ulrich Windl schrieb am 01.06.2021 um 14:57 in Nachricht <60b64b0c.ed38.00a...@rz.uni-regensburg.de>: >>>> Lennart Poettering schrieb am 01.06.2021 um 14:43 in > Nachricht : > > On Di, 01.06.21 14:33, Ulrich Windl (ulrich.wi

[systemd-devel] Antw: [EXT] Re: What causes "systemd-journald[3256]: Missed 127 kernel messages"

2021-06-01 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 01.06.2021 um 13:39 in Nachricht : > On Di, 01.06.21 12:42, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Jun 01 12:33:10 h18 systemd‑journald[3256]: Missed 195 kernel messages >> >> A few questions: >> 1)

[systemd-devel] Antw: [EXT] Re: What causes "systemd-journald[3256]: Missed 127 kernel messages"

2021-06-01 Thread Ulrich Windl
Sorry, once again I forgot to include the list in the reply... >>> Ulrich Windl schrieb am 01.06.2021 um 13:25 in Nachricht <60B61917.C5A : 161 : 60728>: >>>> Reindl Harald schrieb am 01.06.2021 um 12:45 in > Nachricht <54ae14a5-69a2-702c-7146-7d2095beb...@thelou

[systemd-devel] What causes "systemd-journald[3256]: Missed 127 kernel messages"

2021-06-01 Thread Ulrich Windl
Hi! Debugging an issue (a few hundred processes hanging) I used "echo w >/proc/sysrq-trigger". When viewing the journal I found out that it's incomplete, saying (grep Missed): Jun 01 12:33:10 h18 systemd-journald[3256]: Missed 3990 kernel messages Jun 01 12:33:10 h18 systemd-journald[3256]:

[systemd-devel] Antw: [EXT] Re: [dm-devel] RFC: one more time: SCSI device identification

2021-04-27 Thread Ulrich Windl
>>> Hannes Reinecke schrieb am 27.04.2021 um 10:21 in Nachricht <2a6903e4-ff2b-67d5-e772-6971db844...@suse.de>: > On 4/27/21 10:10 AM, Martin Wilck wrote: >> On Tue, 2021‑04‑27 at 13:48 +1000, Erwin van Londen wrote: Wrt 1), we can only hope that it's the case. But 2) and 3) need work,

[systemd-devel] Antw: [EXT] Re: [dm-devel] RFC: one more time: SCSI device identification

2021-04-27 Thread Ulrich Windl
>>> Erwin van Londen schrieb am 27.04.2021 um 05:48 >>> in Nachricht : > > On Mon, 2021-04-26 at 13:16 +, Martin Wilck wrote: >> On Mon, 2021-04-26 at 13:14 +0200, Ulrich Windl wrote: >> > > > >> > > >> > > Whil

[systemd-devel] Antw: [EXT] Re: systemctl reboot get terminated by signal 15

2021-04-26 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 23.04.2021 um 21:33 in Nachricht : > On Fr, 23.04.21 14:15, Pengpeng Sun (pengpe...@vmware.com) wrote: > >> Hi Lennart, >> >> The issue reproduced at 2021‑04‑22T15:45:30.230Z, I ran 'sudo journalctl ‑b', > the log began at Apr 22 15:45:48 which is later than

[systemd-devel] Antw: [EXT] Re: RFC: one more time: SCSI device identification

2021-04-26 Thread Ulrich Windl
>>> Martin Wilck schrieb am 23.04.2021 um 12:28 in Nachricht : > On Thu, 2021‑04‑22 at 21:40 ‑0400, Martin K. Petersen wrote: >> >> Martin, >> >> > I suppose 99.9% of users never bother with customizing the udev >> > rules. >> >> Except for the other 99.9%, perhaps? :) We definitely have many

[systemd-devel] Antw: [EXT] Re: "Correct" way to obtain DHCP lease info?

2021-04-23 Thread Ulrich Windl
>>> "Bruce A. Johnson" schrieb am 22.04.2021 um 22:14 in Nachricht <5aaf83b2-9857-425d-2d7f-b9660abf9...@blueridgenetworks.com>: > I'm still trying to get an explanation of why having a valid DHCP > address is not in itself good enough. The only reason I've been able to > see is that after the

[systemd-devel] Antw: [EXT] Kdump with full-disk LUKS encryption

2021-04-20 Thread Ulrich Windl
>>> Kairui Song schrieb am 19.04.2021 um 12:00 in Nachricht : > Hi all, > > I'm currently trying to add kdump support for systemd with full‑disk > LUKS encryption. vmcores contain sensitive data so they should also be > protected, and network dumps sometimes are not available. So kdump has > to

[systemd-devel] Q: asymmetry of ExecStop and ExecStart

2021-04-14 Thread Ulrich Windl
Hi! I have two services defined, one using ExecStart only, the other ExecStop only. Then I discovered some asymmetry: systemd is still starting the service with the ExecStop only, while the one with the ExecStart only never is stopped. Is that intended, or do I have some configuration error in

[systemd-devel] Antw: [EXT] .local searches not working

2021-04-12 Thread Ulrich Windl
>>> Phillip Susi schrieb am 09.04.2021 um 20:27 in Nachricht <874kgfqphb@vps.thesusis.net>: > What special treatment does systemd‑resolved give to .local domains? > The corporate windows network uses a .local domain and even when I point > systemd‑resolved at the domain controller, it fails

[systemd-devel] Antw: [EXT] Re: Only start a tomcat server when you are sure that time-sync.target is online

2021-03-25 Thread Ulrich Windl
>>> Reindl Harald schrieb am 25.03.2021 um 15:03 in Nachricht : ... > there are really very few cases when Requires is really what someone wants there are really very few cases when someone wants Requires ;-) ___ systemd-devel mailing list

[systemd-devel] Antw: [EXT] Only start a tomcat server when you are sure that time-sync.target is online

2021-03-25 Thread Ulrich Windl
>>> Jan Hugo Prins schrieb am 25.03.2021 um 14:41 in Nachricht <227be317-1e1e-42b9-f871-70b790594...@jhprins.org>: > Hello, > > In our platform we have a dependency where we want to be sure that the > time‑sync.target is online before we start our application servers. We > do this because we

[systemd-devel] Antw: [EXT] Journalctl exits under heavy logs

2021-03-22 Thread Ulrich Windl
>>> Ravindran Shanmugam schrieb am 20.03.2021 um 20:50 in Nachricht : > Hi, > > > > Bug / Issue: > > Under heavy logs entering the systemd-journald, journalctl Exits with one > of the following error messages: > > > > Failed to iterate through journal: Bad message > > Failed to get

Re: [systemd-devel] Antw: [EXT] [PATCH] usb-storage: Add quirk to defeat Kindle's automatic unload

2021-03-19 Thread Ulrich Windl
>>> Alan Stern schrieb am 18.03.2021 um 16:03 in Nachricht <20210318150309.gb527...@rowland.harvard.edu>: > On Thu, Mar 18, 2021 at 08:10:56AM +0100, Ulrich Windl wrote: >> >>> Alan Stern schrieb am 17.03.2021 um 20:06 in >> Nachricht <20210317190654.ga

[systemd-devel] Antw: [EXT] [PATCH] usb-storage: Add quirk to defeat Kindle's automatic unload

2021-03-18 Thread Ulrich Windl
>>> Alan Stern schrieb am 17.03.2021 um 20:06 in Nachricht <20210317190654.ga497...@rowland.harvard.edu>: > Matthias reports that the Amazon Kindle automatically removes its > emulated media if it doesn't receive another SCSI command within about > one second after a SYNCHRONIZE CACHE. It does

[systemd-devel] Antw: [EXT] Re: [usb-storage] Re: Amazon Kindle disconnect after Synchronize Cache

2021-03-18 Thread Ulrich Windl
>>> Matthias Schwarzott schrieb am 17.03.2021 um 18:56 in Nachricht <5f8c0755-0884-f505-c4e8-3a5e89001...@gentoo.org>: > Am 17.03.21 um 16:17 schrieb Alan Stern: >> On Wed, Mar 17, 2021 at 01:21:50PM +0100, Hans de Goede wrote: >>> Hi, >>> >>> On 3/16/21 6:04 PM, Alan Stern wrote: I think it

[systemd-devel] Antw: [EXT] Re: [usb-storage] Re: Amazon Kindle disconnect after Synchronize Cache

2021-03-18 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 17.03.2021 um 17:47 in Nachricht : > On Mi, 17.03.21 11:17, Alan Stern (st...@rowland.harvard.edu) wrote: > >> On Wed, Mar 17, 2021 at 01:21:50PM +0100, Hans de Goede wrote: >> > Hi, >> > >> > On 3/16/21 6:04 PM, Alan Stern wrote: >> > > I think it would be

[systemd-devel] Antw: [EXT] Re: Odd effect when using systemd-analyze verify in RPM %check

2021-03-17 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 15.03.2021 um 17:04 in Nachricht : > On Mo, 15.03.21 16:54, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> While constructing a new RPM package I tried "systemd‑analyze verify" as > %chec

[systemd-devel] Odd effect when using systemd-analyze verify in RPM %check

2021-03-15 Thread Ulrich Windl
;systemd-analyze verify" in an RPM %chehck without having to install half of the system into buildroot? Regards, Ulrich Windl ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Antw: Re: Antw: [EXT] Re: Q; syslog.socket dependency

2021-03-12 Thread Ulrich Windl
>>> Michael Chapman schrieb am 12.03.2021 um 11:27 in Nachricht : > On Fri, 12 Mar 2021, Ulrich Windl wrote: > [...] >> > Can you think of a better way of wording the documentation? >> >> It depends: Do you consider /dev/log to be a "syslog socket"

[systemd-devel] Antw: Re: Antw: [EXT] Re: Q; syslog.socket dependency

2021-03-12 Thread Ulrich Windl
>>> Michael Chapman schrieb am 12.03.2021 um 08:59 in Nachricht <90c9a861-f8cd-88d7-647-c6cc2a8ad...@very.puzzling.org>: > On Fri, 12 Mar 2021, Ulrich Windl wrote: >> >>> Reindl Harald schrieb am 11.03.2021 um 16:23 in >> Nachricht <4422087b

[systemd-devel] Antw: [EXT] Re: Q; syslog.socket dependency

2021-03-11 Thread Ulrich Windl
>>> Reindl Harald schrieb am 11.03.2021 um 16:23 in Nachricht <4422087b-9966-e7fb-66ad-4157d83f2...@thelounge.net>: > > Am 11.03.21 um 12:17 schrieb Ulrich Windl: >> Hi! >> >> I have a unit that uses logger, and I want to run it after syslog is

[systemd-devel] Need help: Program not run when rebooting

2021-03-11 Thread Ulrich Windl
Hi! I tried to write a simple test unit that logs a message when the system is going down (for reboot or halt), but it does not work: --- [Unit] Description=Test Stop log entries Documentation=man:logger(1) DefaultDependencies=no After=local-fs.target Before=reboot.target halt.target

[systemd-devel] Q; syslog.socket dependency

2021-03-11 Thread Ulrich Windl
Hi! I have a unit that uses logger, and I want to run it after syslog is available. So I added syslog.socket as dependency, but it fails: Mar 11 12:11:02 jeos1 systemd[1]: syslog.socket: Socket service syslog.service not loaded, refusing. Mar 11 12:11:02 jeos1 systemd[1]: Failed to listen on

[systemd-devel] Antw: Re: Antw: [EXT] D-bus connection Unknown error

2021-03-03 Thread Ulrich Windl
>>> Reindl Harald schrieb am 03.03.2021 um 12:39 in Nachricht <35c55fcf-6f7c-0566-ef55-5d7b2fb50...@thelounge.net>: > > Am 03.03.21 um 07:59 schrieb Ulrich Windl: >>>>> Shiju Email <994...@gmail.com> schrieb am 02.03.2021 um 22:27 in Nachricht &

[systemd-devel] Antw: [EXT] D-bus connection Unknown error

2021-03-02 Thread Ulrich Windl
>>> Shiju Email <994...@gmail.com> schrieb am 02.03.2021 um 22:27 in Nachricht : > Hi, I am getting an error when any systemctl commands are issued. > > Failed to get D-bus connection: Unknown error -1 I have no idea, but I think "unknown error" is bad programming style; it's like "something

[systemd-devel] Q: Roles for a one-shot service

2021-02-24 Thread Ulrich Windl
parameter to indicate that a boot or shutdown is happening. I'm unsure how to model that with systemd. Should I define one service or three services? Any proposals? Regards, Ulrich Windl ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

[systemd-devel] Antw: Re: Antw: [EXT] Re: Looking for known memory leaks triggered by stress testing add/remove/up/down interfaces

2021-02-19 Thread Ulrich Windl
>>> Reindl Harald schrieb am 19.02.2021 um 09:13 in Nachricht <068b561d-677f-1abf-ef9f-0f43571e1...@thelounge.net>: > > Am 19.02.21 um 08:44 schrieb Ulrich Windl: >>>>> Lennart Poettering schrieb am 18.02.2021 um 19:30 >> in >> Nachricht : &

[systemd-devel] Antw: [EXT] Re: Looking for known memory leaks triggered by stress testing add/remove/up/down interfaces

2021-02-18 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 18.02.2021 um 19:30 in Nachricht : ... > entry instead of asking for new memory again. This allocation cache is > a bit quicker then going to malloc() all the time, but means if you > just watch the heap you'll assume there's a leak even though there > isn't

[systemd-devel] Antw: Re: Antw: [EXT] Re: Q: Debugging missing requirements

2021-02-15 Thread Ulrich Windl
>>> Dave Howorth schrieb am 12.02.2021 um 16:17 in Nachricht <20210212151718.1ff9b...@acer-suse.lan>: > On Fri, 12 Feb 2021 18:04:58 +0300 > Andrei Borzenkov wrote: >> 12.02.2021 10:04, Ulrich Windl пишет: >> >>>> Andrei Borzenkov schrieb am 11

[systemd-devel] Antw: [EXT] Re: Q: Debugging missing requirements

2021-02-11 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 11.02.2021 um 15:20 in Nachricht : > On Thu, Feb 11, 2021 at 1:47 PM Ulrich Windl > wrote: >> >> Hi! >> >> Suspecting systemd added some requirement that isn't fulfilled after boot, > preventing my units from start

[systemd-devel] Antw: Q: Debugging missing requirements

2021-02-11 Thread Ulrich Windl
>>> Ulrich Windl schrieb am 11.02.2021 um 11:46 in Nachricht <60250B22.85D : >>> 161 : 60728>: > Hi! > > Suspecting systemd added some requirement that isn't fulfilled after boot, > preventing my units from starting I wonder: > How can I debug sy

[systemd-devel] Q: Debugging missing requirements

2021-02-11 Thread Ulrich Windl
Hi! Suspecting systemd added some requirement that isn't fulfilled after boot, preventing my units from starting I wonder: How can I debug systemd's requirements checking for units that are enabled, but not started at boot (status "inactive (dead)"? Or another way: Can I list the dependencies

[systemd-devel] Antw: Re: [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-11 Thread Ulrich Windl
>>> Phillip Susi schrieb am 10.02.2021 um 20:39 in >>> Nachricht <878s7v6759@vps.thesusis.net>: > Chris Murphy writes: > >> It's not interleaving. It uses delayed allocation to make random >> writes into sequential writes. It's tries harder to keep file blocks > > Yes, and when you do

[systemd-devel] Antw: [EXT] timesyncd log messages galore

2021-02-11 Thread Ulrich Windl
>>> Ede Wolf schrieb am 10.02.2021 um 19:39 in Nachricht : > Hi, > > > My journal get spammed with messages from timesyncd, claiming a changed > network connection. However, I have not touched the network > configuration at all and the ntp even happens to be on the same subnet. > No DHCP

[systemd-devel] Antw: Re: [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-09 Thread Ulrich Windl
>>> Phillip Susi schrieb am 09.02.2021 um 15:53 in >>> Nachricht <87o8gtz3m1@vps.thesusis.net>: > Chris Murphy writes: > >> Basically correct. It will merge random writes such that they become >> sequential writes. But it means inserts/appends/overwrites for a file >> won't be located with

[systemd-devel] Antw: Re: Antw: Antw: Re: Re: Antw: [EXT] Re: Still confused with socket activation

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 11:28 in Nachricht <74f975f6-1ef2-ee64-bf95-415a5626...@very.puzzling.org>: > On Tue, 9 Feb 2021, Ulrich Windl wrote: > [...] >> OK, I tried (staring libvirtd.service with ‑‑listen and without ‑‑timout): >> Feb 09 10:59

Re: [systemd-devel] Antw: Re: Antw: [EXT] Re: Still confused with socket activation

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 10:17 in Nachricht : > On Tue, 9 Feb 2021, Ulrich Windl wrote: > [...] >> At what timne exactly? When pacemaker starts, or when the systemd using is >> about to be started? > > Pacemaker adds the drop‑in j

[systemd-devel] Antw: Re: Re: Antw: [EXT] Re: Still confused with socket activation

2021-02-09 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 09.02.2021 um 10:14 in Nachricht : > On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl > wrote: >> >> Thanks and "back to the mess": If I use libvirtd.service instead of >> libvirtd-tls.socket, it does *not* open the TLS so

[systemd-devel] Antw: Antw: Re: Re: Antw: [EXT] Re: Still confused with socket activation

2021-02-09 Thread Ulrich Windl
>>> "Ulrich Windl" schrieb am 09.02.2021 um 10:28 in Nachricht <602255b402a10003e...@gwsmtp.uni-regensburg.de>: >>>> Andrei Borzenkov schrieb am 09.02.2021 um 10:14 in > Nachricht > : >> On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl >>

[systemd-devel] Antw: Re: Re: Antw: [EXT] Re: Still confused with socket activation

2021-02-09 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 09.02.2021 um 10:14 in Nachricht : > On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl > wrote: >> >> Thanks and "back to the mess": If I use libvirtd.service instead of >> libvirtd-tls.socket, it does *not* open the TLS so

[systemd-devel] Antw: Re: Antw: [EXT] Re: Still confused with socket activation

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 09:15 in Nachricht <20675743-9521-cdca-1c58-d42de7117...@very.puzzling.org>: > On Tue, 9 Feb 2021, Michael Chapman wrote: > [...] >> Note that when you're using Pacemaker to manage a systemd service, you >> should not enable the service in the normal

[systemd-devel] Antw: Re: Antw: [EXT] Re: Still confused with socket activation

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 09:09 in Nachricht : > On Tue, 9 Feb 2021, Ulrich Windl wrote: > [...] >> As for the drop‑ins: I neither know what those are expected to do, not who >> adds them at run time. See "documentation"... > > The 50

[systemd-devel] Antw: [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-09 Thread Ulrich Windl
>>> Chris Murphy schrieb am 09.02.2021 um 06:13 in Nachricht : > On Mon, Feb 8, 2021 at 7:56 AM Phillip Susi wrote: >> >> >> Chris Murphy writes: >> >> >> It sounds like you are arguing that it is better to do the wrong thing >> >> on all SSDs rather than do the right thing on ones that aren't

Re: [systemd-devel] Antw: [EXT] Re: Still confused with socket activation

2021-02-08 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 08.02.2021 um 19:43 in Nachricht <63608ba2-0510-0e03-eb20-c92d86521...@gmail.com>: > 08.02.2021 12:10, Ulrich Windl пишет: >> It seems systemd messes with that in a bad way. >> > > Streetlight effect ... > > For the

[systemd-devel] Antw: [EXT] Re: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

2021-02-08 Thread Ulrich Windl
>>> Reindl Harald schrieb am 08.02.2021 um 19:01 in Nachricht : > > Am 08.02.21 um 18:27 schrieb Lennart Poettering: >> On So, 07.02.21 22:43, Reindl Harald (h.rei...@thelounge.net) wrote: >> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1909805 >> >> In response to your actual issue,

Re: [systemd-devel] Antw: [EXT] Re: Still confused with socket activation

2021-02-08 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 06.02.2021 um 09:14 in Nachricht <09aa6a69-ee37-ffea-c4fd-e4c5d3327...@gmail.com>: > 04.02.2021 10:47, Ulrich Windl пишет: ... >> I had provided the full units yesterday. Basically I don't know what to do: > I >> just want to

[systemd-devel] Antw: [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-08 Thread Ulrich Windl
>>> Phillip Susi schrieb am 05.02.2021 um 16:02 in Nachricht <87a6si5yjq@vps.thesusis.net>: > Chris Murphy writes: > >> But it gets worse. The way systemd‑journald is submitting the journals >> for defragmentation is making them more fragmented than just leaving >> them alone. > > Wait,

[systemd-devel] Antw: [EXT] Re: Still confused with socket activation

2021-02-04 Thread Ulrich Windl
>>> Ulrich Windl schrieb am 03.02.2021 um 10:34 in Nachricht <601A6E3D.E40 : 161 : 60728>: >>>> Lennart Poettering schrieb am 02.02.2021 um 15:59 in > Nachricht <20210202145954.GB36677@gardel-login>: > > On Di, 02.02.21 10:43, Ulrich Windl (u

[systemd-devel] Antw: [EXT] Re: Still confused with socket activation

2021-02-03 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 03.02.2021 um 19:13 in Nachricht : > 02.02.2021 12:43, Ulrich Windl пишет: >> Hi! >> >> Having: >> --- >> # /usr/lib/systemd/system/virtlockd.service >> [Unit] >> Description=Virtual machine lock mana

[systemd-devel] Antw: [EXT] Limitation on maximum number of systemd timers that can be active

2021-02-03 Thread Ulrich Windl
>>> "P.R.Dinesh" schrieb am 03.02.2021 um 07:46 in >>> Nachricht : > Do we have any limitation on the maximum number of systemd timers / units > that can be active in the system? > Will it consume high cpu/memory if we configure 1000s of systemd timers? What about trying? Probably depends on

[systemd-devel] Antw: [EXT] Re: Still confused with socket activation

2021-02-03 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 02.02.2021 um 15:59 in Nachricht <20210202145954.GB36677@gardel-login>: > On Di, 02.02.21 10:43, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> Having: >> ‑‑‑ >> # /usr/lib/systemd/system

[systemd-devel] Still confused with socket activation

2021-02-02 Thread Ulrich Windl
Hi! Having: --- # /usr/lib/systemd/system/virtlockd.service [Unit] Description=Virtual machine lock manager Requires=virtlockd.socket Requires=virtlockd-admin.socket Before=libvirtd.service ... --- How would I start both sockets successfully unter program control? If I start one socket, I cannot

[systemd-devel] Is it intentional that "systemctl cat" outputs "# /dev/null" for a masked unit?

2021-02-02 Thread Ulrich Windl
Well, the subject says it all: I had masked a socket unit and the related non-socket-unit failed to start. Trying to see the definition of the unit with "systemctl cat" I only saw "# /dev/null". Is that intended? "systemctl show" still shows a lot of data... My idea was when "unmask" knows how

[systemd-devel] Antw: [EXT] Re: Starting a socket unit that finds an active service fails

2021-01-31 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 29.01.2021 um 16:38 in Nachricht <20210129153859.GA31189@gardel-login>: > On Fr, 29.01.21 12:30, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) > wrote: > >> Hi! >> >> I wonder whether this is a bug: >> Wh

[systemd-devel] Starting a socket unit that finds an active service fails

2021-01-29 Thread Ulrich Windl
Hi! I wonder whether this is a bug: When starting a socket unit that finds ist service active already, I get an error systemd[1]: libvirtd-tls.socket: Socket service libvirtd.service already active, refusing. systemd[1]: Failed to listen on Libvirt TLS IP socket. When using systemd units in a

[systemd-devel] Antw: [EXT] Re: successful mount starts a service - how?

2021-01-18 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 19.01.2021 um 06:30 in Nachricht <3a365c71-004e-031e-4153-80c376d80...@gmail.com>: > 19.01.2021 04:00, lejeczek пишет: >> hi guys. >> >> I'm fiddling with it but have run out of options/ideas. >> What I would like to have is systemd starts a service when a device,

[systemd-devel] Antw: Re: Antw: [EXT] emergency shutdown, don't wait for timeouts

2021-01-07 Thread Ulrich Windl
>>> Chris Murphy schrieb am 06.01.2021 um 03:02 in Nachricht : > On Mon, Jan 4, 2021 at 12:43 PM Phillip Susi wrote: >> >> >> Reindl Harald writes: >> >> > i have seen "user manager" instances hanging for way too long and way >> > more than 3 minutes over the last 10 years >> >> The default

[systemd-devel] Antw: Re: Antw: [EXT] emergency shutdown, don't wait for timeouts

2021-01-04 Thread Ulrich Windl
>>> Reindl Harald schrieb am 04.01.2021 um 14:53 in Nachricht <49b8413f-3131-658f-e21a-a1ee448a0...@thelounge.net>: > > Am 04.01.21 um 13:42 schrieb Ulrich Windl: >>>>> Germano Massullo schrieb am 27.12.2020 um >> 14:26 in >> Nachricht : >&g

[systemd-devel] Antw: [EXT] emergency shutdown, don't wait for timeouts

2021-01-04 Thread Ulrich Windl
>>> Germano Massullo schrieb am 27.12.2020 um 14:26 in Nachricht : > Good day, I recently joined apcupsd (APC UPS Power Control Daemon) > package maintainers on Fedora/CentOS/RHEL. > After a power failure, apcupsd shuts down the system with a command > almost identical to > shutdown ‑h ‑H now >

[systemd-devel] Antw: [EXT] Re: Q: (simple) socket activation

2021-01-04 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 21.12.2020 um 16:18 in Nachricht <20201221151821.GC50805@gardel-login>: > On Fr, 18.12.20 08:44, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> I have a simple questi

[systemd-devel] Antw: [EXT] Skip ExecStop after service end or failure

2021-01-04 Thread Ulrich Windl
>>> Robert Dahlem schrieb am 20.12.2020 um 12:48 in Nachricht : > Hi, > > is there a way to NOT run ExecStop, when a service started successfully, > but ends later without being stopped? > > My scenario: I have an ExecStop that should only run after > > systemctl stop XXX.service > >

[systemd-devel] Antw: [EXT] Re: journalctl -f after restart of journald

2021-01-04 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 19.12.2020 um 13:44 in Nachricht <20201219124443.GM48346@gardel-login>: > On Mo, 30.11.20 12:08, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> I just made an "interesting" observation: Wh

[systemd-devel] Antw: [EXT] Re: Why is journalctl -b so slow?

2021-01-04 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 19.12.2020 um 13:34 in Nachricht <20201219123435.GJ48346@gardel-login>: > On Fr, 20.11.20 10:39, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> journactl ‑b is quite fast to display the first li

[systemd-devel] Q: (simple) socket activation

2020-12-17 Thread Ulrich Windl
Hi! I have a simple question: For a socket-unit I have: LISTENUNITACTIVATES [::]:16514libvirtd-tls.socket libvirtd.service I had enabled/started libvirtd.service first, then configured TLS later,

Re: [systemd-devel] Antw: [EXT] Re: Creating executable device nodes in /dev?

2020-12-16 Thread Ulrich Windl
>>> Jarkko Sakkinen schrieb am 15.12.2020 um 05:19 in Nachricht <20201215041903.ga21...@kernel.org>: > On Mon, Dec 14, 2020 at 08:25:50AM +0100, Ulrich Windl wrote: >> >>> Topi Miettinen schrieb am 11.12.2020 um 12:46 in >> Nachricht >> &l

[systemd-devel] Antw: [EXT] Re: Creating executable device nodes in /dev?

2020-12-13 Thread Ulrich Windl
>>> Juan Guerrero schrieb am 11.12.2020 um 13:31 >>> in Nachricht : > Good morning; > > A question can someone help me with this issue: the file */proc/kcore* has > a size of 140G. How can I fix it, I must restart the server or is there > another way to solve it? >

[systemd-devel] Antw: [EXT] Re: Creating executable device nodes in /dev?

2020-12-13 Thread Ulrich Windl
>>> Topi Miettinen schrieb am 11.12.2020 um 12:46 in Nachricht <27796c04-249e-6cf0-c3e1-0fd657a82...@gmail.com>: > On 11.12.2020 12.46, Jarkko Sakkinen wrote: >> On Wed, Dec 09, 2020 at 10:35:21AM +0200, Topi Miettinen wrote: >>> On 9.12.2020 2.15, Jarkko Sakkinen wrote: On Wed, Dec 09, 2020

[systemd-devel] Antw: [EXT] RFC: Moving fully to OpenSSL (aka. stopping support for gnutls/gcrypt)?

2020-12-09 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 09.12.2020 um 10:50 in Nachricht <20201209095057.GA30977@gardel-login>: > Heya! > > Currently, some parts of the systemd tree link against OpenSSL, others > link against gnutls and libgcrypt, and even others support either, > controlled by a compile time switch.

[systemd-devel] Antw: [EXT] Re: Creating executable device nodes in /dev?

2020-12-08 Thread Ulrich Windl
>>> Jarkko Sakkinen schrieb am 09.12.2020 um 01:15 in >>> Nachricht <20201209001521.ga64...@kernel.org>: ... > > What's the data that supports having noexec /dev anyway? With root > access I can then just use something else like /dev/shm mount. > > Has there been out in the wild real world

[systemd-devel] Antw: [EXT] Timestamps in journal during suspend/resume

2020-12-01 Thread Ulrich Windl
Hi! Seeing this before, my guess was that at some point the kernel message buffer is frozen (not read). Then after resume the messages are read from the kernel buffer and logged. Ulrich >>> Paul Menzel schrieb am 01.12.2020 um 12:45 in Nachricht

[systemd-devel] Antw: [EXT] journalctl -f after restart of journald

2020-11-30 Thread Ulrich Windl
Hi! I forgot: What I'd expect at least to see in the "old" journalctl -f is this log message: -- Logs begin at Wed 2020-11-25 11:27:53 CET. -- Nov 30 12:03:27 h19 systemd-journald[957]: Received SIGTERM from PID 1 (systemd). Regards, Ulrich >>> "Ulrich Windl" s

[systemd-devel] journalctl -f after restart of journald

2020-11-30 Thread Ulrich Windl
Hi! I just made an "interesting" observation: When running "journalctl -f" there is no message when journald restarts, meaning you'll have to restart "journalctl -f", too to see any messages after journald has been restarted. Is this the way it is designed? (systemd-234-24.64 of SLES15 SP2)

[systemd-devel] Antw: [EXT] Re: Why is journalctl -b so slow?

2020-11-23 Thread Ulrich Windl
>>> Vito Caputo schrieb am 20.11.2020 um 20:09 in Nachricht <20201120190913.4t4dupzxrshon...@shells.gnugeneration.com>: > On Fri, Nov 20, 2020 at 10:39:14AM +0100, Ulrich Windl wrote: >> Hi! >> >> journactl ‑b is quite fast to display the first lines, but

[systemd-devel] Why is journalctl -b so slow?

2020-11-20 Thread Ulrich Windl
Hi! journactl -b is quite fast to display the first lines, but when I want to see the last lines, it's quite slow. The journal is on BtrFS that is on a hardware RAID made from two SSDs, so the _filesystem_ should not be the problem (actually it seems the journal is in tmpfs actually): ###

[systemd-devel] Antw: Antw: [EXT] Re: Journald retaining logs for only 10 days

2020-11-16 Thread Ulrich Windl
>>> "Ulrich Windl" schrieb am 16.11.2020 um 08:18 in Nachricht <5fb227c402a10003c...@gwsmtp.uni-regensburg.de>: >>>> Vito Caputo schrieb am 14.11.2020 um 21:29 in > Nachricht > <20201114202930.x7wbx4p37bkkw...@shells.gnugeneration.com>: >

[systemd-devel] Antw: [EXT] Re: Journald retaining logs for only 10 days

2020-11-15 Thread Ulrich Windl
>>> Vito Caputo schrieb am 14.11.2020 um 21:29 in Nachricht <20201114202930.x7wbx4p37bkkw...@shells.gnugeneration.com>: > On Sat, Nov 14, 2020 at 09:31:23AM +, Nikolaus Rath wrote: >> Hello, >> >> I just discovered that on one of my systems journald only retains log >> entries for about 10

[systemd-devel] Antw: [EXT] [SPECIFICATION RFC] The firmware and bootloader log specification

2020-11-15 Thread Ulrich Windl
o or what defines t == 0? ... Regards, Ulrich Windl ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Antw: [EXT] Re: date/time set to epoch when using readonly rootfs

2020-10-26 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 23.10.2020 um 13:00 in Nachricht <20201023110051.GA326204@gardel-login>: > On Fr, 23.10.20 10:37, Belisko Marek (marek.beli...@gmail.com) wrote: > >> > > Sorry I mixed up things. Can you pls guide where can I find code which >> > > set date/time from timestamp?

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

2020-10-22 Thread Ulrich Windl
>>> Reindl Harald schrieb am 22.10.2020 um 18:49 in Nachricht <9af67357-feaa-e1c7-291e-afe5f48e8...@thelounge.net>: > > Am 22.10.20 um 16:55 schrieb Dave Howorth: >> On Thu, 22 Oct 2020 15:27:58 +0200 >> Reindl Harald wrote: >>> Am 22.10.20 um 12:59 schrieb Lennart Poettering: On Do,

[systemd-devel] Antw: [EXT] Re: btrfs raid not ready but systemd tries to mount it anyway

2020-10-19 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 16.10.2020 um 17:51 in Nachricht <20201016155115.GB319022@gardel-login>: > On Fr, 16.10.20 17:45, Lennart Poettering (lenn...@poettering.net) wrote: > >> > 2. Debugging with "rd.udev.debug systemd.log_level=debug": >> > The same 10 HDD BTRFS volume with 4 drives

[systemd-devel] Antw: [EXT] Re: "Eye Of Cylon" animation no longer garbles Ctrl-Alt-F9 emergency shell ?

2020-10-16 Thread Ulrich Windl
>>> fox schrieb am 15.10.2020 um 23:36 in Nachricht : >> > It is refreshing to see that the Cylon eye is appearantly no longer >>> making the Ctrl-Alt-F9 emergency shell unusable. > > while I noted that a modified systemd is quick to install, I also should > point out that a compile + install

[systemd-devel] Antw: [EXT] Re: Q: shutdown messages and the lack of such

2020-10-09 Thread Ulrich Windl
>>> Dave Howorth schrieb am 08.10.2020 um 17:44 in Nachricht <20201008164428.55bcf...@acer-suse.lan>: > On Thu, 08 Oct 2020 14:29:24 + > fox wrote: >> > I wonder: Shouldn't here be an infiormational message at least when >> > the shutdown command is entered, and at least a notice message

[systemd-devel] Antw: [EXT] Q: shutdown messages and the lack of such

2020-10-09 Thread Ulrich Windl
>>> fox schrieb am 08.10.2020 um 16:29 in Nachricht <78d3cbcf17099224becfcd371ebb0...@firemail.cc>: >> I wonder: Shouldn't here be an infiormational message at least when >> the shutdown command is entered, and at least a notice message when >> the actual shutdown time has arrived? >> If you

[systemd-devel] Q: shutdown messages and the lack of such

2020-10-08 Thread Ulrich Windl
Hi! I hadn't used shutdown without "now" for a long time, but to day I did: I was surprised about the messages: In traditional UNIX shutdown would announce the shutdown using wall messages. With systemd (in SLES12 SP5 this time) there was no message sent to the users and even in the journal the

[systemd-devel] Antw: Antw: [EXT] Re: Q on serial-getty

2020-10-08 Thread Ulrich Windl
>>> "Ulrich Windl" schrieb am 08.10.2020 um 08:07 in Nachricht <5f7eac8b02a10003b...@gwsmtp.uni-regensburg.de>: >>>> Silvio Knizek schrieb am 07.10.2020 um 21:17 in > Nachricht : >> Am Mittwoch, den 07.10.2020, 08:49 +0200 schrieb Ulrich Wind

[systemd-devel] Antw: [EXT] Re: Q on serial-getty

2020-10-08 Thread Ulrich Windl
>>> Silvio Knizek schrieb am 07.10.2020 um 21:17 in Nachricht : > Am Mittwoch, den 07.10.2020, 08:49 +0200 schrieb Ulrich Windl: >> Hi! >> >> I'm thinking of configuring a serial getty in SLES15 (systemd‑234). First I > found that there is no manual page descri

[systemd-devel] Antw: [EXT] Re: Q on serial-getty

2020-10-07 Thread Ulrich Windl
>>> Mantas Mikulenas schrieb am 07.10.2020 um 08:56 in Nachricht : > On Wed, Oct 7, 2020 at 9:49 AM Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> Hi! >> >> I'm thinking of configuring a serial getty in SLES15 (systemd-234). Fir

[systemd-devel] Q on serial-getty

2020-10-07 Thread Ulrich Windl
Hi! I'm thinking of configuring a serial getty in SLES15 (systemd-234). First I found that there is no manual page describing the service, and second if I use "systemctl show serial-getty" ("systemctl show serial-getty@" does not work), I get some "funny" numbers: ... UID=4294967295

[systemd-devel] Antw: Re: Antw: [EXT] Re: Q: logrotate and "systemctl kill -s HUP ..."

2020-10-06 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 01.10.2020 um 09:22 in Nachricht <20201001072237.GB301913@gardel-login>: > On Mi, 30.09.20 12:52, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> Thanks for the suggestions. Before I work them out, I

[systemd-devel] Antw: [EXT] Re: Q: logrotate and "systemctl kill -s HUP ..."

2020-09-30 Thread Ulrich Windl
>>> Mantas Mikulenas schrieb am 30.09.2020 um 12:26 in Nachricht : > On Wed, Sep 30, 2020 at 11:24 AM Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> Hi! >> >> I have a problem with logrotate: My postrotate command does not seem

[systemd-devel] Antw: Re: Antw: Re: Antw: [EXT] Re: Memory in systemctl status

2020-09-30 Thread Ulrich Windl
>>> Benjamin Berg schrieb am 30.09.2020 um 12:08 in Nachricht <2f6a1d5b102e5dade4f578d6d704b07508d03d50.ca...@sipsolutions.net>: > On Wed, 2020-09-30 at 11:04 +0200, Ulrich Windl wrote: >> > > > Reindl Harald schrieb am 30.09.2020 um 10:56 >> > > &

  1   2   3   4   >