Your message dated Mon, 15 Sep 2025 12:31:17 +0200
with message-id <[email protected]>
and subject line Re: Your mail
has caused the Debian Bug report #702018,
regarding dkms loops infinitely when overflow tmp fills
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
702018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702018
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dkms
Version: 2.2.0.3-1.2
Severity: normal
Hi,
in function invoke_command() of /usr/sbin/dkms (around line 75) you are
waiting for a file to appear that needs to have some contents:
([[ -e && ! -s ]]).
This file is created in $tmp_location which is $TMPDIR or just /tmp.
In case of /tmp being full, the file will be created but won't get any
contents. So at that point dkms will loop forever.
This might sound as a far-fetched case, but as shown in bug #620014
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620014) this really
happens when overflow-/tmp is in use.
As there are other partitions that have some spare disk space, one
solution might be to set $TMPDIR in dkms.conf. Unfortunately this is
sourced after $tmp_location is already set.
Do you have any other idea how to solve this?
Thorsten
--- End Message ---
--- Begin Message ---
Version: 2.3-1
On Fri, 1 Mar 2013 19:41:48 +0100 (CET) Thorsten Alteholz
<[email protected]> wrote:
Package: dkms
Version: 2.2.0.3-1.2
in function invoke_command() of /usr/sbin/dkms (around line 75) you are
waiting for a file to appear that needs to have some contents:
([[ -e && ! -s ]]).
That part has been rewritten in v2.3
This file is created in $tmp_location which is $TMPDIR or just /tmp.
In case of /tmp being full, the file will be created but won't get any
contents. So at that point dkms will loop forever.
As there are other partitions that have some spare disk space, one
solution might be to set $TMPDIR in dkms.conf. Unfortunately this is
sourced after $tmp_location is already set.
Do you have any other idea how to solve this?
since v0.39.17 you can set tmp_location in
/etc/dkms/framework.conf[.d/*.conf]
Andreas
--- End Message ---
