[systemd-devel] connection failure
Hi all, I am trying to use the Docker in GNS3, when I try to launch it show the error as follows, -- The start-up result is done. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request repeated too quickly. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with result 'exit-code'. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has failed. -- -- The result is failed. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'. Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... -- Subject: Unit dnf-makecache.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- 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 dnf-makecache.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dnf-makecache.service has finished starting up. -- -- The start-up result is done. ...skipping... -- -- The start-up result is done. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request repeated too quickly. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with result 'exit-code'. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has failed. -- -- The result is failed. Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'. Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... -- Subject: Unit dnf-makecache.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- 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 dnf-makecache.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dnf-makecache.service has finished starting up. -- -- The start-up result is done. How to rectify this failure to start the docker application thanks in advance, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] connection failure
Hi! This is the wrong list for your question. You should ask this on the help list for your linux distro, it looks like they've configured Docker incorrectly, or there's some extra required setup that you're missing. You can also consult `journalctl -u docker.service` to find clues on why Docker won't start, but your distro's support community is where you should ask for help. This list can't help debug every OS distro, it's only for bugs or problems in systemd itself. In this case, systemd is working perfectly: the docker service is broken, and systemd tells you that it's broken :). Good luck! - Dave On Tue, Jul 2, 2019 at 6:39 AM ABDUL MAJITH wrote: > Hi all, > > I am trying to use the Docker in GNS3, when I try to launch it show the > error as follows, > > -- The start-up result is done. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request > repeated too quickly. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with > result 'exit-code'. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker > Application Container Engine. > -- Subject: Unit docker.service has failed > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit docker.service has failed. > -- > -- The result is failed. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with > result 'service-start-limit-hit'. > Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... > -- Subject: Unit dnf-makecache.service has begun start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- 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 dnf-makecache.service has finished start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit dnf-makecache.service has finished starting up. > -- > -- The start-up result is done. > ...skipping... > -- > -- The start-up result is done. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request > repeated too quickly. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with > result 'exit-code'. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker > Application Container Engine. > -- Subject: Unit docker.service has failed > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit docker.service has failed. > -- > -- The result is failed. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with > result 'service-start-limit-hit'. > Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... > -- Subject: Unit dnf-makecache.service has begun start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- 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 dnf-makecache.service has finished start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit dnf-makecache.service has finished starting up. > -- > -- The start-up result is done. > > How to rectify this failure to start the docker application > > thanks in advance, > > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] connection failure
On Tue, Jul 02, 2019 at 03:39:04PM +0200, ABDUL MAJITH wrote: > Hi all, > > I am trying to use the Docker in GNS3, when I try to launch it show the > error as follows, > > -- The start-up result is done. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request > repeated too quickly. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with > result 'exit-code'. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker > Application Container Engine. > -- Subject: Unit docker.service has failed > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit docker.service has failed. > -- > -- The result is failed. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with > result 'service-start-limit-hit'. > Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... > -- Subject: Unit dnf-makecache.service has begun start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- 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 dnf-makecache.service has finished start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit dnf-makecache.service has finished starting up. > -- > -- The start-up result is done. > ...skipping... > -- > -- The start-up result is done. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request > repeated too quickly. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with > result 'exit-code'. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker > Application Container Engine. > -- Subject: Unit docker.service has failed > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit docker.service has failed. > -- > -- The result is failed. > Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with > result 'service-start-limit-hit'. > Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... > -- Subject: Unit dnf-makecache.service has begun start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- 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 dnf-makecache.service has finished start-up > -- Defined-By: systemd > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit dnf-makecache.service has finished starting up. > -- > -- The start-up result is done. > > How to rectify this failure to start the docker application This is a problem with docker. Nothing to do with the systemd-devel list. Please ask in a forum appropriate for docker issues. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-devel listed as support confuses users (was: connection failure)
Dear systemd folks, On 7/2/19 3:44 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Jul 02, 2019 at 03:39:04PM +0200, ABDUL MAJITH wrote: >> I am trying to use the Docker in GNS3, when I try to launch it show the >> error as follows, >> >> -- The start-up result is done. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request >> repeated too quickly. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with >> result 'exit-code'. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker >> Application Container Engine. >> -- Subject: Unit docker.service has failed >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit docker.service has failed. >> -- >> -- The result is failed. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with >> result 'service-start-limit-hit'. >> Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... >> -- Subject: Unit dnf-makecache.service has begun start-up >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- 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 dnf-makecache.service has finished start-up >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit dnf-makecache.service has finished starting up. >> -- >> -- The start-up result is done. >> ...skipping... >> -- >> -- The start-up result is done. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Start request >> repeated too quickly. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.service: Failed with >> result 'exit-code'. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: Failed to start Docker >> Application Container Engine. >> -- Subject: Unit docker.service has failed >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit docker.service has failed. >> -- >> -- The result is failed. >> Jul 02 15:21:55 reccon.irisa.fr systemd[1]: docker.socket: Failed with >> result 'service-start-limit-hit'. >> Jul 02 15:24:06 reccon.irisa.fr systemd[1]: Starting dnf makecache... >> -- Subject: Unit dnf-makecache.service has begun start-up >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- 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 dnf-makecache.service has finished start-up >> -- Defined-By: systemd >> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit dnf-makecache.service has finished starting up. >> -- >> -- The start-up result is done. >> >> How to rectify this failure to start the docker application > > This is a problem with docker. Nothing to do with the systemd-devel list. > Please ask in a forum appropriate for docker issues. Reading the output above, I can see, why the people contact this mailing list. The output has the systemd-devel list listed as support all over the place. Kind regards, Paul smime.p7s Description: S/MIME Cryptographic Signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd's connections to /run/systemd/private ?
At $JOB, on some of our SLES12 boxes, our logs are getting swamped with messages saying: "Too many concurrent connections, refusing" It's hampering our ability to manage services, e.g.: # systemctl status ntpd Failed to get properties: Connection reset by peer Near as I can tell from a quick read of the source of dbus.c, we're hitting a hard-coded limit of CONNECTIONS_MAX (set to 4096). I think this is related to the number of connections systemd (pid 1) has to /run/systemd/private, but I'm guessing here: # ss -x | grep /run/systemd/private | wc -l 4015 But, despite the almost 4k connections, 'ss' shows that there are no connected peers: # ss -x | grep /run/systemd/private | grep -v -e '* 0' | wc -l 0 The symptom here is that depending on system activity, systemd stops being able to process new requests. systemd allows requests to come in (e.g. via an invocation of 'systemctl', but if I understand the source of dbus.c, when there are too many connections to it's outgoing stream, systemd rejects the efforts, apparently with no retry. When we first spin up a new SLES12 host with our custom services, the number of connections to /run/systemd/private numbers in the mere hundreds. As workloads increase, the number of connections raises to the thousands. Some hosts are plagued with the 'Too many concurrent' connections, some are not. Empirically, all I've been able to see is that the number of systemd's connections to /run/systemd/private tips over 4k. Is my guess about CONNECTIONS_MAX's relationship to /run/systemd/private correct? - I can't demonstrate that there are any consumers of this stream. - I can't explain why the connection count increases over time. - The CONNECTION_MAX constant is hard-coded, and it gets increased every few months/years, but never seems to be expressed as something you can set in a config file. - I don't know what tunables affect the lifetime/culling of those connections. I have a hypothesis that this may be some resource leak in systemd, but I've not found a way to test that. -- Brian Reichert BSD admin/developer at large ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
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 dnf-makecache.service has finished start-up >>> -- Defined-By: systemd >>> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > > Reading the output above, I can see, why the people contact this mailing > list. > > The output has the systemd-devel list listed as support all over the > place. only because of distributions ship stoneage software given that this was fixed years ago and on the other hand common sense tells my when i have a problem like "trying to use the Docker in GNS3" the systemd-*devel* is likely the wrong place https://www.gns3.com/ https://www.docker.com/ how can when trying to marry two completly unrelated packages together and the error is "docker.service: Failed with result 'exit-code'" stating clearly that the process gave a non-zero code back lead to the conclusion it's a systemd topic? "systemctl status docker.service" would even show the process and the return code and then you debug it like any other service with or without systemd by look at logs, google for the return code ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-devel listed as support confuses users (was: connection failure)
Am Di., 2. Juli 2019 um 16:16 Uhr schrieb Paul Menzel : > Reading the output above, I can see, why the people contact this mailing > list. I agree here. While we do have `support-url` which distros can override, Apparently not all of them do. We could probably change our build system, that `support-url` needs to be set explicitly and if unset, no Support URL is printed in the journal output. Just an idea... Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-devel listed as support confuses users (was: connection failure)
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 have `support-url` which distros can > override, Apparently not all of them do. > We could probably change our build system, that `support-url` needs to > be set explicitly and if unset, no Support URL is printed in the > journal output. This, or since the URL leads to [0], it would be also useful to extend the "About systemd-devel" section to provide some kind of warning that this ML is mainly/only for upstream systemd, not for systemd shipped by distributions. [0] https://lists.freedesktop.org/mailman/listinfo/systemd-devel > Just an idea... > > > Michael > -- PGP Key ID: 0xFB738CE27B634E4B signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] connection failure
On Tue, Jul 02, 2019 at 03:39:04PM +0200, ABDUL MAJITH wrote: > Hi all, > > I am trying to use the Docker in GNS3, when I try to launch it show the > error as follows, What kind of distribution is that? We have to report a bug to them, they are spreading false support addresses, > -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Tomasz TorczOnly gods can safely risk perfection, xmpp: zdzich...@chrome.pl it's a dangerous thing for a man. -- Alia ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Startup single step
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, and developers seemed to like it. I personally think it was a handy tool to have in the arsenal, probably not a "use it all the time" kind of thing. It could be triggered via a kernel command line option and in it's simplest form, systemd would start a service and prompt the user before continuing to the next. I know this would change timing and dependencies may have issues but just throwing out the idea. This could possibly even be used to single step through the shutdown of services. Thanks in advance for your attention, -Jay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-devel listed as support confuses users (was: connection failure)
Am Di., 2. Juli 2019 um 18:52 Uhr schrieb František Šumšal : > This, or since the URL leads to [0], it would be also useful to extend > the "About systemd-devel" section to provide some kind of warning that > this ML is mainly/only for upstream systemd, not for systemd shipped by > distributions. Fwiw, I have no problems if systemd related questions that also touch distro specific issues are discussed here. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] EXT : Startup single step
There's supposed to be a confirm.spawn option, but I've never seen it work. -Original Message- From: systemd-devel On Behalf Of Jay Burger Sent: Tuesday, July 02, 2019 1:31 PM To: systemd-devel@lists.freedesktop.org Subject: EXT :[systemd-devel] Startup single step 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, and developers seemed to like it. I personally think it was a handy tool to have in the arsenal, probably not a "use it all the time" kind of thing. It could be triggered via a kernel command line option and in it's simplest form, systemd would start a service and prompt the user before continuing to the next. I know this would change timing and dependencies may have issues but just throwing out the idea. This could possibly even be used to single step through the shutdown of services. Thanks in advance for your attention, -Jay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: Re: systemd-devel listed as support confuses users (was: connection failure)
>>> 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 have `support-url` which distros can >> override, Apparently not all of them do. >> We could probably change our build system, that `support-url` needs to >> be set explicitly and if unset, no Support URL is printed in the >> journal output. > > This, or since the URL leads to [0], it would be also useful to extend > the "About systemd-devel" section to provide some kind of warning that > this ML is mainly/only for upstream systemd, not for systemd shipped by > distributions. > > [0] https://lists.freedesktop.org/mailman/listinfo/systemd-devel 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. Combined with the fact that the user sees nothing while systemd waits for something (like 3 minutes) the user does not know (because he does not see anything on the console) gives the impression that the system "hangs". This is true at least for SLES 12. While the individual cause of such failures may not be systemd, the overall effect of user frustration is very much due to systemd, giving it its bad reputation. So don't worry if people come to complain about many things here. Removing or changing the support URL might help to reduce the traffic here, but it definitely wouldn't help against the bad reputation of systemd. To make systemd better, you really have to listen to the users' problems and actually MAKE IT BETTER. > >> Just an idea... >> >> >> Michael >> > > -- > PGP Key ID: 0xFB738CE27B634E4B ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: Startup single step
>>> 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, and > developers seemed > to like it. I personally think it was a handy tool to have in the arsenal, > probably not > a "use it all the time" kind of thing. My guess is that you actually do not want to single-step systemd, but instead you want to see what goes wrong and maybe ignore some of such failures and continue as if there was no error. Most useful during boots. See my previous message about user frustration and systemd's bad reputation... > > It could be triggered via a kernel command line option and in it's simplest > form, systemd > would start a service and prompt the user before continuing to the next. I > know > this would > change timing and dependencies may have issues but just throwing out the > idea. > > This could possibly even be used to single step through the shutdown of > services. > > Thanks in advance for your attention, > > -Jay > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
