Your message dated Thu, 1 Nov 2007 22:13:58 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448464: dhclient-script: create new_resolv_conf inside tmp
directory
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: dhcp3-client
Version: 3.0.6.dfsg-1
Severity: wishlist
Hi,
could you change the path of new_resolv_conf and use a temporary directory
instead. It seems more logic to create a temporary file inside a temporary
directory.
It can be helpfull in embedded system or live system when you mount /etc
read-only ;)
cheers,
Fathi
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.22-2-amd64
Debian Release: lenny/sid
500 unstable uclibc.debian.net
500 unstable ftp.de.debian.org
500 kernel-dists-trunk kernel-archive.buildserver.net
1 experimental ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
=================================-+-=================
debianutils (>= 2.8.2) | 2.26
dhcp3-common (= 3.0.6.dfsg-1) | 3.0.6.dfsg-1
libc6 (>= 2.6.1-1) | 2.6.1-6
debconf (>= 0.5) | 1.5.16
OR debconf-2.0 |
--- End Message ---
--- Begin Message ---
> So if we create the new resolv.conf in /tmp, the last thing that
> make_resolv_conf() does is move it to /etc, so there's two problems with
> your proposal:
>
> 1) the mv will no longer be atomic
> 2) if /etc is read-only, the mv is going to fail
right, too fast to submit the bug. I noticed (2) after changing the script.
I prefer to close it.
cheers,
Fathi
--- End Message ---
