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

Am 26.08.19 um 08:38 schrieb 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

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am 26.08.19 um 00:19 schrieb Hans-Dieter Doll: > There are also interactive applications started as user sessions. > Some of these must not be killed but terminated by the supervisor, > otherwise we (i.e. our customers) run into trouble. > >

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

Am 23.08.19 um 05:55 schrieb Mantas Mikulėnas: > On Thu, Aug 22, 2019, 16:38 Ulrich Windl > I doubt it's increasing robustness for any existing application as > pid_traditionally was 16 bit. I don't know if some applications try to > sprintf() a pid into a char[6], but if they do,

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

Am 22.08.19 um 15:38 schrieb 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

Re: [systemd-devel] Environment Variables are not getting passed to a child script started from a service

Am 21.08.19 um 18:29 schrieb Debraj Manna: > I am having a unit file like below running on Ubuntu 16.04 with systemd > version 229. > > echo "Starting hadoop-yarn-resourcemanager" > sudo -u yarn /usr/lib/hadoop-yarn/sbin/yarn-daemon.sh start resourcemanager this crap triggers new sessions,

Re: [systemd-devel] EXT :Re: Deferring start of service until file exists

Am 21.08.19 um 06:34 schrieb Reindl Harald: > Am 21.08.19 um 06:10 schrieb Mantas Mikulėnas: >> On Tue, Aug 20, 2019, 20:43 Reindl Harald > <mailto:h.rei...@thelounge.net>> wrote: >> >> Am 20.08.19 um 18:56 schrieb Boyce, Kevin P [US] (AS): >> &

Re: [systemd-devel] EXT :Re: Deferring start of service until file exists

Am 21.08.19 um 06:10 schrieb Mantas Mikulėnas: > On Tue, Aug 20, 2019, 20:43 Reindl Harald <mailto:h.rei...@thelounge.net>> wrote: > > > > Am 20.08.19 um 18:56 schrieb Boyce, Kevin P [US] (AS): > > If this gets figured out, I would lov

Re: [systemd-devel] EXT :Re: Deferring start of service until file exists

Am 20.08.19 um 18:56 schrieb Boyce, Kevin P [US] (AS): > If this gets figured out, I would love to know how to do it as well. > > My experience with systemd is that it will proceed to start other services > once the dependencies have started, not necessarily exited. no that's only true for

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

Am 14.08.19 um 14:59 schrieb 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 schrie

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

Am 14.08.19 um 12:48 schrieb Michael Chapman: > On Wed, 14 Aug 2019, Reindl Harald wrote: >>>> may is ask you to read the thread you are responding to? >>>> nobody is touching the private socket >>> >>> systemctl will mostly use /run/systemd/privat

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

Am 14.08.19 um 12:41 schrieb Michael Chapman: > On Wed, 14 Aug 2019, Reindl Harald wrote: >> 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 the th

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

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 the thing we need to check here is that systemd >> correctly handles junk on the /run/systemd/private socket. The change on >> the systemctl side certainly tries to

Re: [systemd-devel] systemd-readahead: failed to create fanoltify object

Am 13.08.19 um 12:24 schrieb Ranran: > After upgrading kernel in from 3.10 to 4.14.15 (centOS 7), it seems > that all function OK without any issues. > > Except for some print error in boot which I've noticed: > "systemd-readahead[]: failed to create fanoltify object: Function not >

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

Am 07.08.19 um 14:12 schrieb Ulrich Windl: Dave Howorth schrieb am 07.08.2019 um 12:00 in Ubuntu: /bin/systemctl SuSE: /usr/bin/systemctl >>> >>> I guess it should be /sbin/systemctl ;-) >> >> $ systemctl status >> >> is not a privileged command. > > That's one criteria it's

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

Am 07.08.19 um 07:38 schrieb 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 >>

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

Am 06.08.19 um 16:37 schrieb Thomas Güttler: > I just realized that the location of systemctl varies across linux > distributions. > > Ubuntu: /bin/systemctl > SuSE: /usr/bin/systemctl > > Which one do you think is better?

Re: [systemd-devel] systemd.journald.forward_to doesn't forward all journal messages

Am 05.08.19 um 23:08 schrieb Chris Murphy: > And I freely admit that it's rare indeed that both the journal is > unavailable, and there are no useful hints at all forwarded to console > or kmsg. But I'm not even sure it's expected most all of the journal > messages should be forwarded with the

Re: [systemd-devel] Health check for a service managed by systemd

gt; /opt/test/service & > PID=$! > > /bin/systemd-notify --ready > while(true); do >     FAIL=0 >     kill -0 $PID >     if [[ $? -ne 0 ]]; then FAIL=1; fi > > #    curl http://localhost/test/ > #    if [[ $? -ne 0 ]]; then FAIL=1; fi > > if [[ $FAIL -eq 0 ]];

Re: [systemd-devel] Health check for a service managed by systemd

Am 25.07.19 um 20:38 schrieb Debraj Manna: > I have a service on a Ubuntu 16.04 which I use systemctl start, stop, > restart and status to control. > > One time the systemctl status returned active, but the application > "behind" the service responded http code different from 200. > > So I

Re: [systemd-devel] Logs from a service is not showing up in journalctl but showing up in syslog

Am 25.07.19 um 15:46 schrieb Debraj Manna: > Thanks Mantas for replying.  > > ExecStartPre=-/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-prestart.sh" > ExecStart=/bin/su ubuntu -c > "/home/ubuntu/build-target/kafka/kafka-systemd-health.sh" > ExecStopPost=-/bin/bash >

Re: [systemd-devel] failing unmounts during reboot

Am 25.07.19 um 13:29 schrieb Frank Steiner: > Silvio Knizek wrote: > >> the proper approach would be to define the dependency of the generated >> .service to the mount point with a drop-in and RequiresMountsFor=. See >> man:systemd.unit for more information. > > How would that work for init.d

Re: [systemd-devel] failing unmounts during reboot

Am 25.07.19 um 13:15 schrieb Mantas Mikulėnas: > IIRC the idea is that user sessions are killed during shutdown before > unmounting anything anyway, and services have implicit > After=local-fs.target so they get stopped before local filesystems? The > shutdown process is one area that I still

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

Am 25.07.19 um 13:07 schrieb Frank Steiner: > Reindl Harald wrote: > >> "try to kill all processes using a filesystem before unmounting it" >> isn't that easy when it comes to namespaces, "lsof" even don't tell you >> the root cause preventing

Re: [systemd-devel] failing unmounts during reboot

Am 25.07.19 um 12:10 schrieb Silvio Knizek: > the proper approach would be to define the dependency of the generated > .service to the mount point with a drop-in and RequiresMountsFor=. See > man:systemd.unit for more information. > Also the systemd-sysv-generator can only do so much. Please

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

Am 25.07.19 um 12:08 schrieb Ulrich Windl: > Before systemd (almost) all processes were killed before unmounting that's often a transfigured point of view many issues where there also before systemd but never got noticed and after change to systemd they got visible, just because a sysvinit

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

Am 03.07.19 um 11:59 schrieb Ulrich Windl: > Well an actual fact: I upgraded a system yesterday, and I spend about eight > reboots and about 5 hours just to find out WHY systemd booted into an > emergency > shell. Compared to the old init I would have found and fixed that in one boot > I >

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

Am 03.07.19 um 11:53 schrieb Ulrich Windl: > I agree that the major problem with systemd was that distributions switched 3 > or 5 years too early to it. guess where you would be now without them solving most fo the problems over the past years for people coming like you late to the party guess

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

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 emergency shell. this is not true there are very rare cases where you end in the emergency shell > with the fact

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

Am 02.07.19 um 16:10 schrieb Paul Menzel: > Dear systemd folks, > >>> -- Unit dnf-makecache.service has begun starting up. >>> Jul 02 15:24:07 reccon.irisa.fr dnf[18029]: Metadata timer caching disabled. >>> Jul 02 15:24:07 reccon.irisa.fr systemd[1]: Started dnf makecache. >>> -- Subject: Unit

Re: [systemd-devel] swap on zram service unit, using Conflicts=umount

Am 22.06.19 um 18:42 schrieb Chris Murphy: > 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 > certain I understand if it's a good idea or necessary. > >

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

Am 17.06.19 um 16:26 schrieb Lennart Poettering: > On Mo, 17.06.19 16:24, Lennart Poettering (mzn...@0pointer.de) wrote: > > [...] > >> On current Linuxes the assumption tends to be that there's only one >> RPM instance or one admin running at a time, and that they schedule >> the

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

Am 17.06.19 um 16:25 schrieb Lennart Poettering: > On Fr, 31.05.19 14:01, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Am 31.05.19 um 12:31 schrieb Michael Chapman: >>> It also means that the sysadmin can't prepare a set of interconnected >>> changes

Re: [systemd-devel] amavis broken

frankly, could you realize that this is the SYSTEMD mailing list and not every random service failing out there needs to be discussed here? it even tells you the syntax errors in your quote and for anything else call a amavis list that stuff isn't even a systemd unit at all - */etc/init.d/amavis*

Re: [systemd-devel] A lot of programs broken [List in top Bottom] (moovie too big for be published)

Am 14.06.19 um 17:07 schrieb Dorian ROSSE: > Hello, *[list of programs broken : (1) netword-dispatcher , (2) udisks2  > ,  (3) thermald , (4) ModemManager  ,  (5) systemd-logind ,  (6) > avahi-daemon , (7) wpa_supplicant , (8) accounts-daemon , (9) lxc-net , >  (10) ctdb , (11) dnsmasq , (12)

Re: [systemd-devel] SonarQube Service Help

Am 12.06.19 um 18:56 schrieb Hire, Shannon [US] (MS): > I’m not sure if this is the right place to ask for help, but my system > log directed me here. wirte a bugreport for your distribution, that nonsense point to systemd was removed years ago when a service fails > So I currently have

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

Am 11.06.19 um 15:00 schrieb Ulrich Windl: >>>> Reindl Harald schrieb am 11.06.2019 um 14:30 in > Nachricht <917331d8-845f-54d5-908c-e6c7d124a...@thelounge.net>: >> >> Am 11.06.19 um 13:34 schrieb Ulrich Windl: >>> I have a forking service (wi

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

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. In the past I had implemented "rc{service} rotate" to send > SIGHUP to the daemon as "postrotate" action. After converting (actually being > converted

Re: [systemd-devel] Syslog-ng Failed

Am 07.06.19 um 16:14 schrieb Blaise T: > I'm having an issue with my syslog-ng service. I already checked to see > if syslog-ng. service was enabled, which it was. & I ran the syntax > command on syslog-ng & there was no errors. When I try to start the > service, I'm getting an error saying: >

Re: [systemd-devel] User question: how to manage an application split up into multiple binaries The Right Way.

Am 05.06.19 um 10:34 schrieb Etienne Doms: > Hi all, > > We are developing an application on an embedded system which, for some > reasons, must be split up into multiple processes. All these processes > are linked between each other, they communicate using named pipes, and > all of them should

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

Am 05.06.19 um 09:29 schrieb Michael Chapman: > On Wed, 5 Jun 2019, Ulrich Windl wrote: >>>>> 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

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

Am 04.06.19 um 14:20 schrieb Ulrich Windl: >>>> Reindl Harald schrieb am 04.06.2019 um 13:56 in > Nachricht : > > [...] >> BTW: >> >> you could really make your life easier by looking at existing units > > I prefer specifications over examples, bu

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

Am 04.06.19 um 14:17 schrieb Ulrich Windl: >> | or - before an option makes no sense in a INI-syle cofnig > > I don't know the parser any INI style is Key=Value no matter the OS or software BTW: can you please only reply to the list instead reply all, your offlist copy is typically faster

Re: [systemd-devel] Q: ConditionPathExists=

Am 04.06.19 um 13:51 schrieb Reindl Harald: > > > 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/isredir.conf", I

Re: [systemd-devel] Q: ConditionPathExists=

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/isredir.conf", I get a "start condition failed" even if both files exist. why don't you just use

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

Am 03.06.19 um 12:43 schrieb 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 >>>> Re

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

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 >> iotwatch.target get restarted for any reason, then this unit will be >> started again. > > That's a valuable hint: I

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

Am 31.05.19 um 12:31 schrieb Michael Chapman: > It also means that the sysadmin can't prepare a set of interconnected > changes and have them applied at once. For instance, you might want a > timer unit and its associated service unit to be applied at the same time, > rather than have the

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

Am 31.05.19 um 13:28 schrieb Michael Chapman: > 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

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

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 end of the > RPM transaction if units were installed or removed. This is the cleanest > approach since it means all

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

Am 30.05.19 um 16:16 schrieb Roger Pack: > Had a thought the other day... > > Seems like many packages (ex: rpm's) that includes a *.service file > may eventually be required to call > > systemctl daemon-reload > > in the package, for new file changes to "take." > > This causes bugs like >

Re: [systemd-devel] chkconfig on preferred to --add?

Am 23.05.19 um 18:29 schrieb Roger Pack: > As a note, if I have a sysV /etc/init.d/name service that is "turned > on" by "chkconfig --add name" it seems that it adds it to *different > targets* than what "systemctl enable name" does (which appears to run > "chkconfig name on" enabling it for

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

Am 21.05.19 um 10:04 schrieb Zbigniew Jędrzejewski-Szmek: > 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

Re: [systemd-devel] Failed to start apache2 with error code exited 1 failure

Am 20.05.19 um 11:34 schrieb Dorian ROSSE: > Ok I will ask to Apache but I was know this Is a systemd problem because > the engine of Apache is systemd... no! it don't matter who starts httpd, it fails and system is just the messenger as there is pretty clear at least one config error in the

Re: [systemd-devel] ExecStartPre checking conf

Am 19.05.19 um 11:45 schrieb Olaf van der Spek: > ExecStartPre is sometimes used to check the configuration. Does this make > sense? > It seems this causes a lot of code to run twice, as the configuration > is checked on the real invocation anyway. > > [Unit] > Description=Lighttpd Daemon >

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

Am 16.05.19 um 12:41 schrieb Ulrich Windl: >> Please, this is just wasting everyone's time. Take the advice that >> Reindl gave you: generators are an advanced tool that you don't need >> when staring with systemd. > > Yes systemd is for you developers, not for developers like me. Your're the >

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

Am 15.05.19 um 13:12 schrieb Ulrich Windl: >> Well, there can always be more examples, but "generators" are >> inherently an advanced concept: if you are writing a generator, then >> you already should be pro enough to be able to consult the sources of >> the various generators shipped with

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

Am 15.05.19 um 11:25 schrieb Andrei Borzenkov: > On Wed, May 15, 2019 at 12:17 PM Lennart Poettering > wrote: >>> >>> To me it's the most horrible part of systemd: Messing with >>> symlinks... >> >> You should never need to. For all relevant operations there are >> "systemctl" verbs, i.e.

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

Am 14.05.19 um 08:35 schrieb Ulrich Windl: >> stop it - if you would have read IT news (golem/heise) the last 7 years >> or so you would know about /run and why it is a top-directory >> >> https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard >> >> /run >> >> Run-time variable data:

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

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: >>> Can you capture register contents at the point of the crash? >>> >>> Does this reproduce in a chroot? Maybe you can

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

Am 13.05.19 um 09:18 schrieb Ulrich Windl: >>> I didn't see the start of this thread, but is it another attempt to >> re-implement /proc/cpuinfo's flags? >> >> can you please stop all that trolling? > > Actually the number of unfriendly words from your side beat mine by an order > of

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

Am 13.05.19 um 08:20 schrieb Ulrich Windl: >> Note that "/var/run" is a legacy alias for "/run". It's highly >> recommended not to use the former anymore. > > It it because you don't like sub-directories, or is it to save four bytes? > ;-) stop it - if you would have read IT news

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

Am 09.05.19 um 12:25 schrieb Ulrich Windl: > 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

Re: [systemd-devel] systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file

Am 29.04.19 um 21:32 schrieb linuxfr...@gmx.at: > 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 there are still systemd-coredump's

Re: [systemd-devel] How to ensure a systemd unit waits for ntpd to sync before starting?

Am 02.04.19 um 12:34 schrieb Lennart Poettering: > On Di, 02.04.19 13:01, Mantas Mikulėnas (graw...@gmail.com) wrote: > >> On Tue, Apr 2, 2019 at 12:33 PM Reindl Harald >> wrote: >> >>> can you please stop cure replys instead just post to the list breaking &g

Re: [systemd-devel] How to ensure a systemd unit waits for ntpd to sync before starting?

can you please stop cure replys instead just post to the list breaking others threading and reply-list buttons? Am 02.04.19 um 11:25 schrieb Debraj Manna: > I do see a ntp-wait . >  Can some one let me know what > corresponding condition I should place in my

Re: [systemd-devel] How to ensure a systemd unit waits for ntpd to sync before starting?

Am 02.04.19 um 09:44 schrieb Debraj Manna: > > We have a service that starts at boot. We need to ensure it doesn't > start until the system clock has been synchronized via ntp. The > machines are using |ntpd| After=ntpd.service Wants=ntpd.service

Re: [systemd-devel] can I use network-online.target without NM and networkd

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 using ifup configuration for network so can I > use this target to be sure

Re: [systemd-devel] udp socket-activation "fake-service"

Am 18.03.19 um 17:29 schrieb Reindl Harald: > Am 18.03.19 um 11:31 schrieb Reindl Harald: >> Am 18.03.19 um 10:54 schrieb Lennart Poettering: >>> I am not fully grokking what you are trying to do, but to recv UDP >>> dgrams you'd have to write a tiny

Re: [systemd-devel] systemd-activation: it's a mess for beginners

Am 20.03.19 um 21:10 schrieb Daniele Nicolodi: > On 20-03-2019 14:01, Reindl Harald wrote: >> Am 20.03.19 um 20:53 schrieb Daniele Nicolodi: >>> I am not sure what you are trying to say, but the first source code >>> snippet in your email in not valid C code.

Re: [systemd-devel] systemd-activation: it's a mess for beginners

Am 20.03.19 um 20:52 schrieb Mantas Mikulėnas: > On Wed, Mar 20, 2019 at 9:46 PM Reindl Harald wrote: >> >> http://0pointer.de/blog/projects/socket-activation.html >> >> - >> >> #include >> #include >&

[systemd-devel] systemd-activation: it's a mess for beginners

http://0pointer.de/blog/projects/socket-activation.html - #include #include #include #include #include #include #include #include #include #include #include #include int fd; if(sd_listen_fds(0) != 1) { fprintf(stderr, "No or too many

Re: [systemd-devel] Why ExecStop when service receives SIGTERM?

Am 18.03.19 um 20:23 schrieb Felipe Gasper: >> On Mar 18, 2019, at 2:54 PM, Reindl Harald wrote: >> >> Am 18.03.19 um 19:27 schrieb Felipe Gasper: >>> I’m noticing that ExecStop handlers execute not merely as a means for >>> systemd to stop a Servi

Re: [systemd-devel] Why ExecStop when service receives SIGTERM?

Am 18.03.19 um 19:27 schrieb Felipe Gasper: > I’m noticing that ExecStop handlers execute not merely as a means for > systemd to stop a Service but also when that Service’s main process receives > SIGTERM. > > The documentation (systemd.service) says that ExecStop commands are how

Re: [systemd-devel] udp socket-activation "fake-service"

Am 18.03.19 um 11:31 schrieb Reindl Harald: > Am 18.03.19 um 10:54 schrieb Lennart Poettering: >> I am not fully grokking what you are trying to do, but to recv UDP >> dgrams you'd have to write a tiny program that calls recvfrom() (or a >> similar syscall)

Re: [systemd-devel] udp socket-activation "fake-service"

Am 18.03.19 um 10:54 schrieb Lennart Poettering: > On Sa, 16.03.19 05:52, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Hi >> >> for a firewall development setup (nested virtualization) i have running >> a tcp service like below on a VM liesting on a comple

Re: [systemd-devel] install ipsec and l2tp problem

Am 16.03.19 um 06:27 schrieb Li Haosen: > hello,dear,Engineer,Forgive me,my English not good,i install ipsec and > l2tp has some problem,i can‘t find how to solve,can help me?   > 1.jpg > 2.jpg for sure not with ugly screenshots "systemctl status" and "journalctl" combined with copy as

[systemd-devel] udp socket-activation "fake-service"

Hi for a firewall development setup (nested virtualization) i have running a tcp service like below on a VM liesting on a complete /24 network behind a NAT with "udpsvd" at least something works for "nmap -p 53 -sU -P0 host" on a single port and always running - is there some way to get a

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

Am 07.03.19 um 18:48 schrieb Tomasz Torcz: > On Thu, Mar 07, 2019 at 11:24:08AM +0100, Lennart Poettering wrote: >> 2. rtags (it uses default.target in a socket file, which is even >>weirder, should use sockets.target) > > sockets.target is rather odd for me. If I had (hypothetical) >

Re: [systemd-devel] How to set custom default target permanently?

Am 05.03.19 um 21:16 schrieb ashitha v: > How can I change the default.target to a custom.target permanently? When > the image is booting, it is set to multi-user.target by creating a > symlink from /etc/systemd/system/default.target. If I do systemctl > set-default custom.target, then the

Re: [systemd-devel] Testing if timesyncd is synced

Am 20.02.19 um 18:36 schrieb Mantas Mikulėnas: > adjtimex(2) the kernel syscall has existed since kernel 2.4.x at least, > possibly even as far back as 1.0. It's older than systemd-timesyncd in > any case. > > Others apparently were talking about /bin/adjtimex the standalone > executable, which

Re: [systemd-devel] Testing if timesyncd is synced

Am 20.02.19 um 14:00 schrieb Aurelian Melinte: > Some (old?) systems do not have adjtimex: > > $ adjtimex > > -bash: adjtimex: command not found but which systems don't have a package manager to install whatever you want? [harry@srv-rhsoft:~]$ adjtimex bash: adjtimex: command not found

Re: [systemd-devel] Which unit type and which parameter to use

Am 17.02.19 um 04:04 schrieb Dequan Zhang: > I have a cli application that will be opened when remote user log in > through ssh. > > Should I create a service file for such application?  > > And since CLI requires a controlling terminal, what should I do to set > up the unit file?  > > Last,

Re: [systemd-devel] Question on Before=

Am 02.02.19 um 21:05 schrieb Steve Dickson: > On 2/2/19 2:52 PM, Reindl Harald wrote: >> Am 02.02.19 um 20:42 schrieb Steve Dickson: >>> Hello, >>> >>> In a.service I have >>> >>> [Unit] >>> Before=b.service >>> >&

Re: [systemd-devel] Question on Before=

Am 02.02.19 um 21:03 schrieb Steve Dickson: > On 2/2/19 2:48 PM, Tomasz Torcz wrote: >> On Sat, Feb 02, 2019 at 02:42:15PM -0500, Steve Dickson wrote: >>> Hello, >>> >>> In a.service I have >>> >>> [Unit] >>> Before=b.service >>> >>> [Install] >>> RequiredBy=b.service >>> >>> when I systemd

Re: [systemd-devel] Question on Before=

Am 02.02.19 um 20:42 schrieb Steve Dickson: > Hello, > > In a.service I have > > [Unit] > Before=b.service > > [Install] > RequiredBy=b.service > > when I systemd start b.service (which happens to fail) > but... a.service is not being run. > > So I guess my question is what do I have to

Re: [systemd-devel] systemctl condreload - Is it a thing?

Am 30.01.19 um 17:07 schrieb Ian Pilcher: > $SUBJECT pretty much says it all.  It seems to work, but I can't find > any mention of it in the documentation or with my Google searches. > > Is it deprecated and going away? "condrestart" and "condreload" are working just fine and aliases for

Re: [systemd-devel] journald cves on 239

Am 24.01.19 um 15:34 schrieb Umut Tezduyar Lindskog: > Hello, > > We are on systemd 239 and we would like to patch following CVEs > without jumping to 240. > > CVE-2018-16864 > CVE-2018-16865 > CVE-2018-16866 > > Can someone please help us out and point the commits that we need to > back-port

Re: [systemd-devel] graphical sessions inherits display-maanger only partly

Am 22.01.19 um 08:12 schrieb Mantas Mikulėnas: > On Tue, Jan 22, 2019 at 3:46 AM Reindl Harald <mailto:h.rei...@thelounge.net>> wrote: > > > "ProtectSystem=full" with the setup below just works, "su -" in a > konsole within the gr

[systemd-devel] graphical sessions inherits display-maanger only partly

"ProtectSystem=full" with the setup below just works, "su -" in a konsole within the graphical session don't gain write permissions Tasks: 4 why? shouldn't everything started after the graphical login interherit any settings from teh display-manager service and run under it's cgroup?

Re: [systemd-devel] Conflation of propagation in dependencies creates race windows

Am 19.01.19 um 17:58 schrieb Uoti Urpala: > On Sat, 2019-01-19 at 15:54 +, Jonathon Kowalski wrote: >> https://github.com/systemd/systemd/issues/1154 which is similar in >> nature convinces me that systemd currently conflates two many >> properties in the same dependency. The second bug in

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

Am 17.01.19 um 18:51 schrieb Christopher Cox: > On 1/17/19 11:21 AM, Reindl Harald wrote: >> >> Am 17.01.19 um 18:17 schrieb Christopher Cox: >>> On 1/17/19 11:01 AM, Lennart Poettering wrote: >>>> Hmm, what kind of processes are you missing? user session st

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

Am 17.01.19 um 18:17 schrieb Christopher Cox: > On 1/17/19 11:01 AM, Lennart Poettering wrote: >> Hmm, what kind of processes are you missing? user session stuff? How >> do you shut down? Note that display managers are likely to terminate >> the user sessions first, and only initiate system

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

Am 17.01.19 um 17:00 schrieb Christopher Cox: > On 1/16/19 11:10 PM, Reindl Harald wrote: >> that all is not really new and was not better with sysvinit, it only was >> slow enough, full of sleep/usleep hacks and so most of the time by luck >> worked but with no guarantes

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

Am 17.01.19 um 06:04 schrieb Jonathon Kowalski: > On Thu, Jan 17, 2019 at 4:49 AM Christopher Cox wrote: >> Adding some extra systemd clarification. Saying do this After or Before >> other >> service doesn't mean the start/stop completes before moving on. It may >> execute >> asynchronously

Re: [systemd-devel] Bugfix release(s)

Am 14.01.19 um 16:48 schrieb Lennart Poettering: > On Mo, 14.01.19 08:43, Dave Reisner (d...@falconindy.com) wrote: >> systemd needs better release hygiene, not just a smattering of bugfix >> releases. As a rolling release distro, we regularly find release-day >> blockers. That's bad for

[systemd-devel] systemd-journald.service not using ProtectSystem=strict?

looking at the current security issues and how it triggers the troll-army i wonder why systemd-journald.service is not restricted from at least write to /usr and /root at least on Fedora 28 (that it's not vulernable because of compiler hardening is just luck) [root@testserver:~]$ cat

Re: [systemd-devel] MongoDB error after the changing the Path

Am 09.01.19 um 16:17 schrieb Hemanth Kumar: > Can you share me MongoDB users Google -> "Mongodb community support" https://www.mongodb.com/community-support-resources ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] Requires and After

Am 03.01.19 um 01:38 schrieb Tom H: > What Reindl Harald was saying was that "Requires" should have an > implicit "After" because it wouldn't make sense for a.service to > require b.service but to start before b.service exactly and i don't get the discussion f

Re: [systemd-devel] Requires and After

Am 02.01.19 um 22:09 schrieb James Feeney: > On 1/2/19 3:21 AM, Reindl Harald wrote: >> it's >> pretty obvious when i REQUIRE something that it should be there when i >> get started > > Not only is it not "obvious" that "something should be ther

Re: [systemd-devel] .service and .socket

Am 02.01.19 um 12:12 schrieb Michael Chapman: > On Wed, 2 Jan 2019, Reindl Harald wrote: >> Am 02.01.19 um 11:49 schrieb Michael Chapman: >>> On Wed, 2 Jan 2019, Reindl Harald wrote: >>> [...] >>>> agreed, but why can't have socket simply optional a [

<    1   2   3   4   5   6   7   8   9   10   >