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
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
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
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
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
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
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.
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
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
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,
> --
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.
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
12 matches
Mail list logo
