I just disabled LLMNR by putting LLMNR=no in resolved.conf to see if it helps,
but it still crashes as before.
Jan 03 12:16:23 system1 systemd-resolved[863]: Got DNS stub UDP query packet
for id 10122
Jan 03 12:16:23 system1 systemd-resolved[863]: Looking up RR for
54.49.125.74.in-addr.arpa IN
Package: systemd
Version: 247.3-7+deb11u4
Severity: critical
File: systemd-resolved
Justification: breaks the whole system
X-Debbugs-Cc: cor...@gmx.de
Dear Maintainer,
systemd-resolved takes up all memory on certain PTR queries within only a few
milliseconds and is then oom-killed. This sometime
Package: linux-2.6
Version: 2.6.32-38
Severity: important
When doing a "cat /proc/self/mountinfo" inside a guest the result is "Cannot
allocate memory".
What really makes it evil: the page cache of the whole machine is flushed and
all swap space available consumed. This effectively causes the w
Package: openssh-server
Version: 1:5.5p1-6+squeeze1
Severity: important
It seems that the sftp server does a seek just after opening a file. This
results in a seek error when trying to access files which are not seekable
(like /proc entries).
A suggested fix: if llseek fails (for SET, 0), just
Hi,
I'm still not sure if it's a kernel bug/misbehavior, as bash works fine
on the same system. And even if it's a kernel bug, shouldn't dash
contain the same work-around as bash seems to have?
Fact is, when upgrading debian (and so dash becomes the default shell)
some applications break bec
Package: dash
Version: 0.5.5.1-2.3
Severity: important
The 'read' command seems to only read the first character and not the whole
line.
Example / comparison with bash:
# /bin/dash
# read MAX
Package: spfquery
Version: 1.2.9-1
Severity: normal
After upgrading spfquery a lot of mails got refused by our mailserver.
It turned out spfquery changed a lot of their return codes (for
example before success was 1, now it is 2; temp dns-failure was 5,
now it is 6). Also some arguments seem to
7 matches
Mail list logo
