Processing commands for cont...@bugs.debian.org:
> tags 925190 +fixed-upstream
Bug #925190 [udev] udev: Random execution order of RUN commands
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
925190: https://bugs.debian.org/cgi-bin/bugr
It looks like it's actually already fixed upstream.
https://github.com/systemd/systemd/issues/11368
Fixed by the commit:
https://github.com/systemd/systemd/commit/39a15c8a8dad26deda140867f03e44a535b7bd8d
> Versions of packages udev is related to:
> ii systemd 241-1
By looking at the debian sour
Package: udev
Version: 241-2
Severity: important
Dear Maintainer,
It looks like the udev RUN commands are executed in a random order. This
can have catastrophic consequences during boot.
For instance, 69-bcache.rules as provided by bcache-tools try to load
the kernel module with a RUN{builtin} c
Dear Sir/Madam,
ATOS group companies are leaders in digital services with proforma annual
revenue of circa ? 13 billion and circa 100,000 employees in 73 countries,
serving a global client base.
We strive to create the firm of the future. We believe that bringing together people,
business &
Control: tags -1 + moreinfo
Am 20.03.19 um 19:24 schrieb Michael Biebl:
> Am 20.03.19 um 19:19 schrieb Michael Biebl:
>> Am 20.03.19 um 19:01 schrieb Laurent Bonnaud:
>>> Timestamp generators-start: Wed 2019-03-20 15:06:27 CET
>>> Timestamp generators-finish: Wed 2019-03-20 15:06:38 CET
>>
>> That
Processing control commands:
> tags -1 + moreinfo
Bug #925160 [systemd] systemd: user session slow to start (11 seconds)
Added tag(s) moreinfo.
--
925160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Am 20.03.19 um 19:19 schrieb Michael Biebl:
> Am 20.03.19 um 19:01 schrieb Laurent Bonnaud:
>> Timestamp generators-start: Wed 2019-03-20 15:06:27 CET
>> Timestamp generators-finish: Wed 2019-03-20 15:06:38 CET
>
> That is odd.
> Do you have any (user) generators which might take a long time?
Typ
Am 20.03.19 um 19:01 schrieb Laurent Bonnaud:
> Timestamp generators-start: Wed 2019-03-20 15:06:27 CET
> Timestamp generators-finish: Wed 2019-03-20 15:06:38 CET
That is odd.
Do you have any (user) generators which might take a long time?
--
Why is it that all of the instruments seeking intell
On 3/20/19 5:47 PM, Michael Prokop wrote:
> What do you mean with "Further connections are fast", ssh-ing into
> the system as the same user ?
Exactly.
> (do you use ssh with ControlMaster?)
I do not use ControlMaster.
> Is connecting via `ssh -o ControlPath=none ...` also slow?
Using the "-
On 3/20/19 5:47 PM, Michael Prokop wrote:
> Just a quick shot, are you sure your reverse DNS is OK?
Yes.
> If you set `UseDNS no` in /etc/ssh/sshd_config, is the SSH login faster?
Setting "UseDNS no" does not solve the problem.
Thanks,
--
Laurent.
___
On 3/20/19 5:52 PM, Michael Biebl wrote:
> Is this problem reproducible if you login locally?
Sorry, I will have to wait until tomorrow to have physical access to this
system...
Thanks,
--
Laurent.
___
Pkg-systemd-maintainers mailing list
Pkg-syste
On 20.03.19 17:36, Laurent Bonnaud wrote:
> Package: systemd
> Version: 241-2
> Severity: important
>
>
> Dear Maintainer,
>
> on this system, an initial ssh connection needs 11 seconds to complete (as
> root or any other user). Further connections are fast.
Is this problem reproducible if yo
* Laurent Bonnaud [Wed Mar 20, 2019 at 05:36:44PM +0100]:
> on this system, an initial ssh connection needs 11 seconds to complete (as
> root or any other user). Further connections are fast.
> This is not a slow boot problem because it occurs even when the machine has
> been booted for days.
Package: systemd
Version: 241-2
Severity: important
Dear Maintainer,
on this system, an initial ssh connection needs 11 seconds to complete (as root
or any other user). Further connections are fast.
This is not a slow boot problem because it occurs even when the machine has
been booted for da
Control: retitle -1 restart logind on package updates
Control: block -1 by 798097
On Thu, 28 Feb 2019 15:09:14 -0600 "Karl O. Pinc" wrote:
> If systemd restarts all of its processes which are affected
> by package upgrade then the only reason to require a restart would
> be if some changes in new
Processing control commands:
> retitle -1 restart logind on package updates
Bug #919509 [systemd] systemd packaging does not touch /var/run/reboot-required
Changed Bug title to 'restart logind on package updates' from 'systemd
packaging does not touch /var/run/reboot-required'.
> block -1 by 7980
Your message dated Wed, 20 Mar 2019 10:31:26 +0100
with message-id
and subject line Re: Bug#923674: systemd: test-stat-util fails with SIGABRT
when /dev/random is bind-mounted from /dev/urandom
has caused the Debian Bug report #923674,
regarding systemd: test-stat-util fails with SIGABRT when /de
Am 18.03.19 um 22:00 schrieb Nico Haase:
> Dear Mika, dear Michael,
>
> thank you for your answers and apologies for answering them so late.
>
> Am 07.03.2019 um 09:15 schrieb Michael Prokop:
>> * Nico Haase [Thu Mar 07, 2019 at 08:33:57AM +0100]:
>>> Package: systemd
>>> Version: 241-1~bpo9+1
>>
Your message dated Wed, 20 Mar 2019 09:47:12 +0100
with message-id
and subject line Re: Bug#924575: systemd-networkd doesn't process IPv6 RA
properly
has caused the Debian Bug report #924575,
regarding systemd-networkd doesn't process IPv6 RA properly
to be marked as done.
This means that you cl
Am 18.03.19 um 20:46 schrieb Jean-Pierre:
> Hi,
>
> Any news about a fix ?
>
> Or maybe an URL where I could submit a patch ?
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924255
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Eart
20 matches
Mail list logo
