[systemd-devel] Antw: Re: rdrand generated with march=winchip-c6 in systemd-241

2019-05-13 Thread Ulrich Windl
>>> tedheadster schrieb am 11.05.2019 um 19:19 in >>> Nachricht : > On Sat, May 11, 2019 at 12:30 PM Florian Weimer wrote: >> Can you capture register contents at the point of the crash? >> >> Does this reproduce in a chroot? Maybe you can trace the whole thing >> with a debugger. Does the

[systemd-devel] Antw: Re: Antw: Re: rdrand generated with march=winchip-c6 in systemd-241

2019-05-13 Thread Ulrich Windl
>>> Reindl Harald schrieb am 13.05.2019 um 09:14 in Nachricht : > > Am 13.05.19 um 09:10 schrieb Ulrich Windl: >>>>> tedheadster schrieb am 11.05.2019 um 19:19 in > Nachricht >> : >>> On Sat, May 11, 2019 at 12:30 PM Florian Weimer wrote: >

[systemd-devel] Antw: Re: Explain status "Loaded: not-found (Reason: No such file or directory)"

2019-05-12 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 09.05.2019 um 16:32 in Nachricht <11c2e9e7-4094-7c65-5840-9f69b54e3...@gmail.com>: > 09.05.2019 13:25, Ulrich Windl пишет: >> Hi! >> >> I'm developing a service and getting the status of my target gives: >> ● iotwa

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

2019-05-13 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 09.05.2019 um 17:24 in Nachricht <20190509152440.GC5854@gardel-login>: > On Do, 09.05.19 12:27, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> Whenever I try to enable or disable a target (th

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

2019-05-12 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 09.05.2019 um 16:54 in Nachricht <399aa684-a6bf-af19-dd09-bd670ec60...@gmail.com>: > 09.05.2019 13:22, Ulrich Windl пишет: >> Hi! >> >> I had to subscribe to this list, even though I'm no systemd fan. Still I'll > have to

[systemd-devel] Antw: Re: Explain status "Loaded: not-found (Reason: No such file or directory)"

2019-05-13 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 09.05.2019 um 17:08 in Nachricht <20190509150818.GA5854@gardel-login>: > On Do, 09.05.19 12:25, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) > wrote: > >> Hi! >> >> I'm developing a service and getting the statu

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

2019-05-13 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 09.05.2019 um 17:28 in Nachricht <20190509152826.GD5854@gardel-login>: > On Do, 09.05.19 15:52, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> (Sorry, I didn't sent to the list before) >> >>> Ulric

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

2019-05-13 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 09.05.2019 um 17:20 in Nachricht <20190509152036.GB5854@gardel-login>: > On Do, 09.05.19 12:22, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> I had to subscribe to this list, even though I'm no

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

2019-05-12 Thread Ulrich Windl
>>> Michael Biebl schrieb am 09.05.2019 um 16:56 in Nachricht : > 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:2

[systemd-devel] Antw: Re: Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Trent Piepho schrieb am 15.05.2019 um 18:54 in >>> Nachricht <1557939250.4229.111.ca...@impinj.com>: > On Wed, 2019-05-15 at 10:03 +, systemd-devel- > requ...@lists.freedesktop.org wrote: >> >> >> If you are looking for a generic converter of foreign stuff into >> classic, persistent

[systemd-devel] Antw: Re: Q: ConditionPathExists=

2019-06-04 Thread Ulrich Windl
>>> Reindl Harald schrieb am 04.06.2019 um 13:51 in Nachricht : > > Am 04.06.19 um 13:32 schrieb Ulrich Windl: >> Hi! >> >> I have a question for ConditionPathExists: >> If I specify two files like "ConditionPathExists=/etc/idredir.conf > /etc

[systemd-devel] Antw: Re: Q: ConditionPathExists=

2019-06-04 Thread Ulrich Windl
example, assuming the example is correct. Still I think the language in the manual could be somewhat more precise. [...] > ConditionPathExists=/dev/tty0 I can only guess that multiple file names are not allowed for ConditionPathExists to allow file names containing spaces, an off concept for UNIX, BT

[systemd-devel] Q: ConditionPathExists=

2019-06-04 Thread Ulrich Windl
Do I have to write "|ConditionPathExists=..." or "ConditionPathExists=|..."? Regards, Ulrich Windl ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Wtrlt: Re: Antw: Re: Unexplainable unit restart ("Start request repeated too quickly")

2019-06-04 Thread Ulrich Windl
(Forgot to reply to all) --- Begin Message --- >>> Michael Chapman schrieb am 04.06.2019 um 11:04 in Nachricht : > On Tue, 4 Jun 2019, Ulrich Windl wrote: >> >>> Michael Chapman schrieb am 03.06.2019 um 13:14 in >> Nachricht : >> [...] >> &

[systemd-devel] Unexplainable unit restart ("Start request repeated too quickly")

2019-06-03 Thread Ulrich Windl
Hi! When installing a test package, I noticed that one unit (iotwatch-generator.service) triggered a restart for an unknown reason. The status is (note: no reason for restart shown): # systemctl status iotwatch-generator.service -l ● iotwatch-generator.service - I/O performance monitor instance

[systemd-devel] Antw: Re: Unexplainable unit restart ("Start request repeated too quickly")

2019-06-03 Thread Ulrich Windl
>>> Michael Chapman schrieb am 03.06.2019 um 10:44 in Nachricht : > On Mon, 3 Jun 2019, Ulrich Windl wrote: >> Hi! >> >> When installing a test package, I noticed that one unit >> (iotwatch-generator.service) triggered a restart for an unknown reaso

Re: [systemd-devel] Antw: Re: Unexplainable unit restart ("Start request repeated too quickly")

2019-06-03 Thread Ulrich Windl
>>> Michael Chapman schrieb am 03.06.2019 um 11:39 in Nachricht : > On Mon, 3 Jun 2019, Ulrich Windl wrote: > [...] >> Hi! >> >> The generator unit is: >> [Unit] >> Description=I/O performance monitor instance generator >> Documentatio

[systemd-devel] Antw: Re: Antw: Re: Unexplainable unit restart ("Start request repeated too quickly")

2019-06-03 Thread Ulrich Windl
>>> Reindl Harald schrieb am 03.06.2019 um 12:35 in Nachricht : > > Am 03.06.19 um 12:30 schrieb Ulrich Windl: >>> That looks fine, though it _might_ make sense for it to have >>> RemainAfterExit= turned on. After all, if default.target or >>> io

[systemd-devel] Antw: Re: suggestion: auto reload as the default to help packagers?

2019-06-03 Thread Ulrich Windl
>>> Michael Chapman schrieb am 31.05.2019 um 13:28 in Nachricht : > On Fri, 31 May 2019, Reindl Harald wrote: >> Am 31.05.19 um 12:31 schrieb Michael Chapman: >> > For RPM on Fedora, the systemd package has %transfiletriggerin and >> > %transfiletriggerun scriptlets that run automatically at the

[systemd-devel] Antw: Re: Antw: Re: suggestion: auto reload as the default to help packagers?

2019-06-03 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 03.06.2019 um 09:48 in Nachricht : > 03.06.2019 10:15, Ulrich Windl пишет: >>>>> Michael Chapman schrieb am 31.05.2019 um 13:28 in >> Nachricht : >>> On Fri, 31 May 2019, Reindl Harald wrote: >>>> Am 31

[systemd-devel] Antw: Re: Antw: Re: Q: ConditionPathExists=

2019-06-05 Thread Ulrich Windl
>>> Reindl Harald schrieb am 04.06.2019 um 14:23 in Nachricht <4e4bc6ca-2637-b10d-f4f6-536f45264...@thelounge.net>: > > Am 04.06.19 um 14:17 schrieb Ulrich Windl: [...] > BTW: can you please only reply to the list instead reply all, your > offlist copy is t

Re: [systemd-devel] Antw: Re: Unexplainable unit restart ("Start request repeated too quickly")

2019-06-04 Thread Ulrich Windl
>>> Michael Chapman schrieb am 03.06.2019 um 13:14 in Nachricht : [...] > > Um, OK. I don't think we're any closer to solving your problem though. :-) Actually I am! The root of the problem is that any oneshot service without RemainAfterExit=true is listed as "inactive (dead)" after being

[systemd-devel] Where to send replies to? (Was: Q: ConditionPathExists=)

2019-06-05 Thread Ulrich Windl
>>> Reto schrieb am 06.06.2019 um 06:16 in Nachricht <20190606041625.2hmr3z6ogqppqkr4@feather.localdomain>: > On Wed, Jun 05, 2019 at 12:26:56PM +0200, Jetchko Jekov wrote: >> Or you (@Reindl) can just fix it on your side and stop ranting and >> imposing your world view on others. > > It *is*

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

2019-06-11 Thread Ulrich Windl
Hi! I have a forking service (with a PID file) that can reopen the logfile after receiving SIGHUP. In the past I had implemented "rc{service} rotate" to send SIGHUP to the daemon as "postrotate" action. After converting (actually being converted ;-)) to systemd I dropped the LSB script, and

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

2019-06-11 Thread Ulrich Windl
GHUP to the main process, you should add a `--kill-who=main` Thanks! I wasn't aware of systemctl's "kill". Regards, Ulrich > > All documented nicely in > https://www.freedesktop.org/software/systemd/man/systemctl.html > > Am Di., 11. Juni 2019 um 13:34 Uhr schrieb

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

2019-06-11 Thread 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 the logfile after > receiving SIGHUP.

[systemd-devel] Anybody care to fix the list processor?

2019-06-11 Thread Ulrich Windl
Hi! Does anybody running the list care to fix the list-processor. The welcome message says: You can also make such adjustments via email by sending a message to: systemd-devel-requ...@lists.freedesktop.org What you get is: The mail system : host

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

2019-05-09 Thread Ulrich Windl
Hi! I had to subscribe to this list, even though I'm no systemd fan. Still I'll have to deal with it as the distribution we use switched to systemd... I'm porting my LSB code to systemd, and I'm having some trouble. Cause of the trouble (and possible reason for systemd's unpopularity) seems to

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

2019-05-09 Thread Ulrich Windl
(Sorry, I didn't sent to the list before) >>> Ulrich Windl schrieb am 09.05.2019 um 13:22 in Nachricht <5cd44c66.ed38.00a...@rz.uni-regensburg.de>: >>>> Michael Biebl schrieb am 09.05.2019 um 12:29 in Nachricht > : > > Am Do., 9. Mai 2019 um 12:27 Uhr sch

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

2019-05-09 Thread Ulrich Windl
(Sorry, I didn't sent to the list before) >>> Ulrich Windl schrieb am 09.05.2019 um >>> 14:25 in Nachricht <5cd44c9a.ed38.00a...@rz.uni-regensburg.de>: >>>> Michael Biebl schrieb am 09.05.2019 um 12:26 in >>>> Nachricht > : > > Hi >

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

2019-05-09 Thread 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 Biebl schrieb am 09.05.2019 um 12:29 in >>>> Nachricht > : > &

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

2019-05-09 Thread Ulrich Windl
(Sorry, I didn't send to the list before) >>> Ulrich Windl schrieb am 09.05.2019 um >>> 14:34 in Nachricht <5cd44ccd.ed38.00a...@rz.uni-regensburg.de>: >>>> Michael Biebl schrieb am 09.05.2019 um 12:43 in >>>> Nachricht > : > &

[systemd-devel] Explain status "Loaded: not-found (Reason: No such file or directory)"

2019-05-09 Thread Ulrich Windl
Hi! I'm developing a service and getting the status of my target gives: ● iotwatch.target Loaded: not-found (Reason: No such file or directory) Active: active since Thu 2019-05-09 12:00:56 CEST; 18min ago I guess it's not a file named "Reason" that's missing. Despite of my recommendation

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

2019-05-09 Thread 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? Regards, Ulrich ___ systemd-devel mailing list

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

2019-05-09 Thread 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? Regards, Ulrich ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

[systemd-devel] Antw: Re: Antw: Re: Antw: Re: rdrand generated with march=winchip-c6 in systemd-241

2019-05-14 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 13.05.2019 um 09:45 in Nachricht <20190513074503.GB9036@gardel-login>: > On Mo, 13.05.19 09:18, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > > Please guys, stop it. > >> > cpuid has *nothing* to d

[systemd-devel] The first and the last things in systemd's lifecycle

2019-05-14 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 14.05.2019 um 08:40 in Nachricht : > On Tue, May 14, 2019 at 9:35 AM Ulrich Windl > wrote: > >> >> I knew that. It doesn't answer _why_ /var/run is obsolete. >> > > /var/run needs /var which is not guaranteed to be

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

2019-05-14 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 14.05.2019 um 10:55 in Nachricht <20190514085558.GD21579@gardel-login>: > On Di, 14.05.19 08:01, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) > wrote: > >> > systemd matches these UNIX semantics closely: we output error m

[systemd-devel] Antw: Re: Antw: Re: Explain status "Loaded: not-found (Reason: No such file or directory)"

2019-05-14 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 13.05.2019 um 09:46 in Nachricht <20190513074653.GC9036@gardel-login>: > On Mo, 13.05.19 07:48, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> >> I guess it's not a file named "Reason" that's missing. D

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

2019-05-14 Thread Ulrich Windl
>>> František Šumšal schrieb am 13.05.2019 um 17:13 in Nachricht <064ac942-a4d7-b547-0705-22f3262f5...@sumsal.cz>: > On 5/13/19 8:20 AM, Ulrich Windl wrote: > >>> "systemd‑analyze verify" exists. Since a long long time. >> >> Not really: Yo

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

2019-05-14 Thread Ulrich Windl
>>> Reindl Harald schrieb am 13.05.2019 um 08:25 in Nachricht <19612492-4b1e-0d87-5360-a67893873...@thelounge.net>: > > Am 13.05.19 um 08:20 schrieb Ulrich Windl: >>> Note that "/var/run" is a legacy alias for "/run". It's hi

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

2019-05-14 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 13.05.2019 um 09:35 in Nachricht <20190513073539.GA9036@gardel-login>: > On Mo, 13.05.19 08:25, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> >> Whenever I try to enable or disable a target (that exists), I get &

[systemd-devel] Antw: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 14.05.2019 um 20:21 in Nachricht : > 14.05.2019 16:39, Ulrich Windl пишет: >> Hi! >> >> Developing my first systemd service I have some problems I don't understand: >> After installation, I get this status: &

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

2019-05-14 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 14.05.2019 um 16:15 in Nachricht <20190514141520.GA22136@gardel-login>: > On Di, 14.05.19 16:07, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hmm, like this:? >> > systemd‑analyze verify /run/systemd/gene

[systemd-devel] Q: Reducing the output of systemctl status

2019-05-15 Thread Ulrich Windl
Hi! First, is it a well-known bug that "--quitet" seems to be ignored for "systemctl status"? It's the only command where --quiet makes sense IMHO, but it seems to have no effect in v228. Also, considering this example output: --- ● iotwatch@LOC1.service - iotwatch I/O performance monitor

[systemd-devel] Antw: Re: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 15.05.2019 um 09:21 in Nachricht : > On Wed, May 15, 2019 at 9:01 AM Ulrich Windl > wrote: >> >> >>> Andrei Borzenkov schrieb am 14.05.2019 um 20:21 in >> Nachricht : >> > 14.05.2019 16:39, Ulrich Windl пишет

[systemd-devel] Slice question

2019-05-15 Thread Ulrich Windl
Hi! When I tried to put the instances of my service into a specific slice (by only specifying the name), I just got an error message. I had: [Service] Slice=something in the service unit file. Amazingly systemd does put my instances in a slice when I removed that Slice line. The slice is

[systemd-devel] systemd-tmpfiles-setup.service failed due to LDAP resolving

2019-05-22 Thread Ulrich Windl
Hi! Obviously the owner of a temporary directory cannot be an LDAP user: # systemctl status systemd-tmpfiles-setup -l ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset:

[systemd-devel] Antw: Re: Failed to open system journal: Invalid argument

2019-05-22 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 22.05.2019 um 10:34 >>> in Nachricht <20190522083459.GC30001@gardel-login>: > On Mi, 22.05.19 01:03, Kay One (kayone...@gmail.com) wrote: > >> Hi Lennart, >> >> Do you have any idea that UBIFS supports writable memory mappings or >> not? > > No idea, sorry! >

[systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

2019-05-22 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 22.05.2019 um 10:32 in Nachricht <20190522083211.GB30001@gardel-login>: > On Di, 21.05.19 17:41, Dorian ROSSE (dorianbr...@hotmail.fr) wrote: > >> Hello everybody, >> >> >> I know this isn’t a bug or a systemd problems but It keeps the >> system in thought of

[systemd-devel] Antw: Re: systemd-tmpfiles-setup.service failed due to LDAP resolving

2019-05-22 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 22.05.2019 um 10:30 in Nachricht <20190522083028.GA30001@gardel-login>: > On Mi, 22.05.19 10:02, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> Obviously the owner of a temporary directory cannot be

Re: [systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

2019-05-22 Thread Ulrich Windl
t; > > De : Dorian ROSSE > Envoyé : Wednesday, May 22, 2019 12:58:15 PM > À : Ulrich Windl; Lennart Poettering > Cc : systemd‑de...@lists.freedesktop.org > Objet : RE: Antw: Re: [systemd‑devel] dbus‑daemon keep shown as zombie process > why ? >

[systemd-devel] Antw: Re: Q: Wants and WantedBy links in generated units and circular dependencies

2019-05-23 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 23.05.2019 um 12:41 in Nachricht : > On Thu, May 23, 2019 at 11:56 AM Ulrich Windl > wrote: >> >> Hi! >> >> After seeing that systemd generators are run as the very first step in >> systemd's life (deduced from t

[systemd-devel] Q: Wants and WantedBy links in generated units and circular dependencies

2019-05-23 Thread Ulrich Windl
Hi! After seeing that systemd generators are run as the very first step in systemd's life (deduced from the timestamps), I quit the idea of using them, and started to use another sort of generator: I have a generator target, that creates another target and a few service targets. The interesting

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-20 Thread Ulrich Windl
>>> 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 read the page again, it's not more clea

[systemd-devel] Does "systemctl daemon-reload" discard service information?

2019-05-20 Thread Ulrich Windl
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: h02:~ # systemctl status iotwatch@* ● iotwatch@VAR.service - iotwatch I/O performance monitor instance "VAR" Loaded: loaded (/etc/iotwatch.conf;

[systemd-devel] Antw: Re: Does "systemctl daemon-reload" discard service information?

2019-05-21 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 20.05.2019 um 19:07 in Nachricht <4d103eef-d000-c9b2-9f7a-e0cda8ed6...@gmail.com>: > 20.05.2019 16:36, Ulrich Windl пишет: >> Hi! >> >> I have had the effect that a "systectl status" before and after a >> "d

[systemd-devel] Antw: Re: Does "systemctl daemon-reload" discard service information?

2019-05-21 Thread Ulrich Windl
>>> Zbigniew Jedrzejewski-Szmek schrieb am 21.05.2019 um 10:04 in Nachricht <20190521080428.go9...@in.waw.pl>: > On Mon, May 20, 2019 at 03:36:28PM +0200, Ulrich Windl wrote: >> Hi! >> >> I have had the effect that a "systemctl status" before and

[systemd-devel] Antw: Re: Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-16 Thread Ulrich Windl
>>> Zbigniew Jedrzejewski-Szmek schrieb am 16.05.2019 um 12:13 in Nachricht <20190516101348.gn9...@in.waw.pl>: > On Thu, May 16, 2019 at 12:04:28PM +0200, Ulrich Windl wrote: >> >>> Lennart Poettering schrieb am 16.05.2019 um 10:29 >> in >> N

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-16 Thread Ulrich Windl
>>> 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 read the page again, it's not more clea

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-16 Thread Ulrich Windl
n imagine is that those "link messing" is needed to provide functionality the systemd actually lacks. Regards, Ulrich >>> Lennart Poettering 05/15/2019, 12:22 PM >>> On Mi, 15.05.19 12:08, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > > I mean, if y

[systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 15.05.2019 um 11:31 in Nachricht <20190515093135.GF22719@gardel-login>: > On Mi, 15.05.19 11:29, Jérémy ROSEN (jeremy.ro...@smile.fr) wrote: > >> well, in another thread, it was discussed why generated should never have >> an install section and why enablement

[systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 15.05.2019 um 11:54 in Nachricht <20190515095443.GA22887@gardel-login>: > On Mi, 15.05.19 12:47, Andrei Borzenkov (arvidj...@gmail.com) wrote: > >> > > localhost:~ # systemctl enable usr‑local.mount >> > > Failed to enable unit: Unit

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 15.05.2019 um 12:04 in Nachricht <20190515100400.GB22945@gardel-login>: > On Mi, 15.05.19 12:01, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> > Writing a generator is not a typical user would do. It's what a >&g

[systemd-devel] Antw: Re: Q: Reducing the output of systemctl status

2019-05-15 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 15.05.2019 um 11:04 >>> in Nachricht <20190515090447.GA22719@gardel-login>: [...] >> I just noticed: If you use a "argv[0] override" for your command, it's not >> just that the command is started with that name, it's also displayed as >> ExecStart here (not

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 15.05.2019 um 12:03 in Nachricht <20190515100311.GA22945@gardel-login>: > On Mi, 15.05.19 11:57, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> >> could call "systemctl add‑wants ‑‑transient" to do th

Re: [systemd-devel] Antw: Re: Antw: Re: Re: "bad" status for genersated target; why?

2019-05-15 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 15.05.2019 um 12:20 in Nachricht <20190515102024.GB23038@gardel-login>: > On Mi, 15.05.19 12:12, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) > wrote: > >> >>> Lennart Poettering schrieb am 15.05.2019 um 12:04 >

[systemd-devel] "bad" status for genersated target; why?

2019-05-14 Thread Ulrich Windl
Hi! Developing my first systemd service I have some problems I don't understand: After installation, I get this status: # systemctl status iotwatch.target ● iotwatch.target - iotwatch I/O performance monitor Loaded: loaded (/run/systemd/generator.late/iotwatch.target; bad; vendor

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

2019-05-14 Thread Ulrich Windl
>>> František Šumšal schrieb am 14.05.2019 um 15:46 in Nachricht : > On 5/14/19 8:39 AM, Ulrich Windl wrote: >>>>> František Šumšal schrieb am 13.05.2019 um 17:13 in >> Nachricht <064ac942-a4d7-b547-0705-22f3262f5...@sumsal.cz>: >>> On 5/13/19 8:20

[systemd-devel] Antw: Re: Antw: Startup single step

2019-07-03 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 03.07.2019 um 11:01 in Nachricht <20190703090130.GB12011@gardel-login>: > On Mi, 03.07.19 08:42, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> >>> Jay Burger schrieb am 02.07.2019 um 19:30 in >> N

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

2019-07-03 Thread Ulrich Windl
>>> František Šumšal schrieb am 02.07.2019 um 18:51 in Nachricht : > > On 7/2/19 4:36 PM, Michael Biebl wrote: >> 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

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

2019-07-03 Thread Ulrich Windl
>>> František Šumšal schrieb am 03.07.2019 um 11:01 in Nachricht : [...] > Honestly, I'm kind of impressed you stamp the "bad bad systemd" phrase all > over > the place several times in your emails, yet you still expect people to be > able > to (willingly) help you. I may have an opinion,

[systemd-devel] systemd-tmpfiles-setup.service: ... Unknown user '1019'

2019-07-03 Thread Ulrich Windl
Hi! I'm having a problem created by systemd: A temporary directory is to be created that is owned by a user found in LDAP. However as all temporary directories are created way before networking is available, I cannot user the user name, nor can systemd delay creating that directory after

[systemd-devel] Antw: Startup single step

2019-07-03 Thread Ulrich Windl
>>> Jay Burger schrieb am 02.07.2019 um 19:30 in Nachricht : > Hi, > > I am curious if there is a way to single step through the systemd startup > of services? I don't find any such feature and am curious what others would > think of it. We had a similar feature in a previous life, different OS,

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

2019-07-05 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 03.07.2019 um 13:30 in Nachricht <20190703113048.GC12226@gardel-login>: > On Mi, 03.07.19 08:37, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> >> I agree here. While we do have `support‑url` which distros can &

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

2019-07-05 Thread Ulrich Windl
>>> Reindl Harald schrieb am 03.07.2019 um 14:01 in Nachricht : > > Am 03.07.19 um 08:37 schrieb Ulrich Windl: >> The really annoying thing with systemd is that if SOMETHING fails during > boot, >> the complete boot is aborted and you are put into an emergenc

[systemd-devel] Antw: Re: Is "systemctl status --state=failed" expected to fail silently?

2019-07-09 Thread Ulrich Windl
>>> 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 being ignored sile

[systemd-devel] Is "systemctl status --state=failed" expected to fail silently?

2019-07-09 Thread Ulrich Windl
Hi! It seems "--state=failed" is being ignored silently for "systemctl status" (in version 228). Is this by design? Regards, Ulrich ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

[systemd-devel] Antw: Re: Anybody care to fix the list processor?

2019-07-01 Thread Ulrich Windl
>>> Simon McVittie schrieb am 11.06.2019 um 16:29 in >>> Nachricht <20190611142939.GA6676@horizon>: > On Tue, 11 Jun 2019 at 15:44:07 +0200, Ulrich Windl wrote: >> Does anybody running the list care to fix the list-processor. > > I don't think

Re: [systemd-devel] Antw: Re: Antw: Re: failing unmounts during reboot

2019-07-29 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 29.07.2019 um 14:16 in Nachricht <20190729121614.GG19185@gardel-login>: > On Mo, 29.07.19 14:14, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) > wrote: > >> OK: The "abandoned" scope most likely is a daemon proc

[systemd-devel] Antw: Re: systemd's connections to /run/systemd/private ?

2019-08-14 Thread Ulrich Windl
>>> Michael Chapman schrieb am 14.08.2019 um 11:47 in Nachricht : > On Wed, 14 Aug 2019, Lennart Poettering wrote: >> Quite frankly, invoking generic UNIX programs with fds < 3 closed is a >> really bad idea in general. That systemctl nowadays is particularly >> careful and deals with situations

[systemd-devel] Antw: Re: Antw: Re: systemd's connections to /run/systemd/private ?

2019-08-14 Thread Ulrich Windl
>>> Reindl Harald schrieb am 14.08.2019 um 12:22 in Nachricht <13150bf2-e0c9-063a-9026-ac95c1fda...@thelounge.net>: > > Am 14.08.19 um 12:10 schrieb Ulrich Windl: >>>>> Michael Chapman schrieb am 14.08.2019 um 11:47 in >>> That's all true, but th

[systemd-devel] Antw: Re: Need help detecting local/remote targets

2019-08-21 Thread Ulrich Windl
>>> Mantas Mikulenas schrieb am 21.08.2019 um 06:07 in Nachricht : > On Wed, Aug 21, 2019, 01:15 Tony Rodriguez wrote: > >> I modified systemd-219 functionality to meet a custom requirement for >> detecting filesystems/devices that use iscsi without using the _netdev >> keyword in /etc/fstab.

[systemd-devel] Antw: systemd prerelease 243-rc2

2019-08-22 Thread Ulrich Windl
>>> systemd tag bot schrieb am 22.08.2019 um 13:56 in Nachricht <20190822115637.1.05c510c92b339...@refi64.com>: > A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the > tarball here: > * On 64 bit systems, the "kernel.pid_max" sysctl is now bumped to >

[systemd-devel] Antw: Re: help: unmounting iscsi xfs filesystem without using netdev in /etc/fstab

2019-08-27 Thread Ulrich Windl
>>> Michael Chapman schrieb am 27.08.2019 um 11:33 in Nachricht : > On Tue, 27 Aug 2019, Tony Rodriguez wrote: >> Managed to detect/mount iscsi devices without using _netdev keyword in >> /etc/fstab. Made changes within src/fstab‑generator/ftstab‑generator.c and it >> seems to work. The only

[systemd-devel] /etc/fstab obsolete?

2019-08-28 Thread Ulrich Windl
Hi! systemd in SLES 12 is causing endless frustration here: Yesterday I was migrating some filesystems to a new device (multipath, MD-RAID, LVM, filesystem, mountpoints, etc.), updating /etc/fstab and other files as needed. After migration was successful, I also cleaned up the now obsolete

[systemd-devel] Antw: Re: /etc/fstab obsolete?

2019-08-28 Thread Ulrich Windl
>>> František Šumšal schrieb am 28.08.2019 um 10:18 in Nachricht : > On 8/28/19 9:33 AM, Ulrich Windl wrote: >> Hi! >> >> systemd in SLES 12 is causing endless frustration here: >> >> Yesterday I was migrating some filesystems to a new device (multipath

[systemd-devel] Antw: Re: /etc/fstab obsolete?

2019-08-28 Thread Ulrich Windl
>>> Frans de Boer schrieb am 28.08.2019 um 11:24 in Nachricht <46281377-9749-7f60-f818-fa8b5d3f4...@fransdb.nl>: [...] >>> That is why I hate systemd! >> believe it: systemd hates you too Yeah, I feel it was written especially for me! ;-) [...] > righteous posture of some people, just because

[systemd-devel] Antw: Re: Antw: systemd prerelease 243-rc2

2019-08-26 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 22.08.2019 um 16:19 >>> in Nachricht <20190822141902.GA585@gardel-login>: [...] > Ahum, this change is a single line added to a default sysct.d/ file we > ship. I mean, you may have your opinions, but this line is not applied > in PID 1 at all, it doesn't touch

[systemd-devel] Antw: Re: Antw: systemd prerelease 243-rc2

2019-08-26 Thread Ulrich Windl
>>> Mantas Mikulenas schrieb am 23.08.2019 um 05:55 in Nachricht : > On Thu, Aug 22, 2019, 16:38 Ulrich Windl > wrote: > >> >>> systemd tag bot schrieb am >> 22.08.2019 >> um >> 13:56 in Nachricht <20190822115637.1.05c510c92b339...@refi

[systemd-devel] Antw: Re: Antw: systemd prerelease 243-rc2

2019-08-26 Thread Ulrich Windl
>>> Tomasz Torcz schrieb am 22.08.2019 um 19:28 in Nachricht <20190822172855.ga159...@mother.pipebreaker.pl>: > On Thu, Aug 22, 2019 at 03:38:05PM +0200, Ulrich Windl wrote: >> >>> systemd tag bot schrieb am 22.08.2019 >> um >> 13:56 in Nachricht

Re: [systemd-devel] Antw: Re: /etc/fstab obsolete?

2019-09-01 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 29.08.2019 um 16:13 in Nachricht <20190829141317.GB9510@gardel-login>: [...] > However, you are coming to this mailing list, in search for free > support, and just dump insults and hate mails onto our doorstep, all > the time. It's just massively annoying. Can't

[systemd-devel] Antw: Re: Antw: Re: /etc/fstab obsolete?

2019-09-02 Thread Ulrich Windl
>>> Andy Pieters schrieb am 02.09.2019 um 10:52 in Nachricht : > On Mon, 2 Sep 2019 at 06:44, Ulrich Windl > wrote: > [...] > Ulrich, we all know by now how you feel about this matter, so why not stop > with belabouring that point. Just point out the problems you a

[systemd-devel] Antw: Re: Antw: Re: /etc/fstab obsolete?

2019-08-28 Thread Ulrich Windl
Hi! I agree to almost everything, except: The handling of /etc/fstab is a true mess. Maybe other config files are handles similarly, but I haven't discovered. For some reason SLES does not set up a German keyboard in the mergency shell (just to make things worse). I had opened a service

[systemd-devel] Antw: Re: /etc/fstab obsolete?

2019-08-29 Thread Ulrich Windl
>>> Lennart Poettering schrieb am 28.08.2019 um 14:41 in Nachricht <20190828124149.GA8141@gardel-login>: > On Mi, 28.08.19 09:33, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> systemd in SLES 12 is causing endless frustration her

[systemd-devel] Antw: Re: Antw: Re: /etc/fstab obsolete?

2019-08-29 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 28.08.2019 um 19:11 in Nachricht <93874740-4d8e-14fc-d92a-17c691c20...@gmail.com>: > 28.08.2019 11:38, Ulrich Windl пишет: >> >> Some design concepts in systemd are just insane, the fstab issue being a > good >> ex

[systemd-devel] Antw: systemd prerelease 243-rc1

2019-07-31 Thread Ulrich Windl
>>> systemd tag bot schrieb am 30.07.2019 um 19:09 in Nachricht <20190730170916.1.c7b12db1b9d29...@refi64.com>: > A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the > tarball here: > > https://github.com/systemd/systemd/archive/v243-rc1.tar.gz > > NOTE: This is

[systemd-devel] Antw: Re: Antw: failing unmounts during reboot

2019-08-05 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 01.08.2019 um 20:38 in Nachricht : > 29.07.2019 9:38, Ulrich Windl пишет: >>>>> Ulrich Windl schrieb am 29.07.2019 um 08:23 in Nachricht <5D3E90D1.4EC : 161 > : >> 60728>: >>>>>> Frank Steiner schrieb am

[systemd-devel] Antw: /bin/systemctl vs /usr/bin/systemctl

2019-08-06 Thread Ulrich Windl
>>> Thomas Güttler schrieb am 06.08.2019 um 16:37 in Nachricht <3243dc34-4eec-e3a0-c6fd-491fdfcaf...@thomas-guettler.de>: > I just realized that the location of systemctl varies across linux > distributions. > > Ubuntu: /bin/systemctl > SuSE: /usr/bin/systemctl I guess it should be

[systemd-devel] Antw: Re: Antw: /bin/systemctl vs /usr/bin/systemctl

2019-08-07 Thread Ulrich Windl
>>> Dave Howorth schrieb am 07.08.2019 um 12:00 in Nachricht <20190807110029.0bdf9...@acer-suse.lan>: > On Wed, 07 Aug 2019 07:38:47 +0200 > "Ulrich Windl" wrote: >> >>> Thomas Güttler schrieb am >> >>> 06.08.2019 um >>

  1   2   3   4   >