NetBSD Problem Report #9657

Received: (qmail 15197 invoked from network); 22 Mar 2000 02:33:42 -0000
Message-Id: <200003220233.VAA01222@zorkmid.mit.edu>
Date: Tue, 21 Mar 2000 21:33:08 -0500 (EST)
From: John Hawkinson <jhawk@mit.edu>
Reply-To: jhawk@mit.edu
To: gnats-bugs@gnats.netbsd.org
Subject: dhclient requires writable leases file
X-Send-Pr-Version: 3.95

>Number:         9657
>Category:       bin
>Synopsis:       dhclient requires writable leases file
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    mellon
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 21 18:36:01 +0000 2000
>Closed-Date:    Sun Apr 08 21:07:27 +0000 2001
>Last-Modified:  Sun Apr 08 21:07:27 +0000 2001
>Originator:     John Hawkinson
>Release:        1.4.2
>Organization:
	MIT
>Environment:

System: NetBSD zorkmid.mit.edu 1.4.2 NetBSD 1.4.2 (GENERIC) #3: Wed Mar 15 23:41:54 PST 2000 toddpw@vader.toddpw.net:/usr/src/sys/arch/i386/compile/GENERIC i386


>Description:
	dhclient really wants to be able to write to /var/db/dhclient_leases,
and will refuse to get a lease if it cannot do so. Unfortunately, there
are are plenty of times where you might want to get a dhcp
lease without a writable /var (e.g. single-user mode). dhclient should
allow you to get a lease without being able to write out the leases
file.

	Perhaps such behavior should be controlled by a command-line
option.

>How-To-Repeat:

>Fix:
	A crude workaround would be to run dhclient under chroot(8)
I don't think that's really acceptable though.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: bin-bug-people->mellon 
Responsible-Changed-By: fair 
Responsible-Changed-When: Thu Mar 22 10:50:24 PST 2001 
Responsible-Changed-Why:  
Ted Lemon is our DHCP expert. 

State-Changed-From-To: open->closed 
State-Changed-By: mellon 
State-Changed-When: Sun Apr 8 14:05:58 PDT 2001 
State-Changed-Why:  
The client no longer considers the inability to write a lease file to be 
a fatal error, except when sending DHCPRELEASE messages.   In the case of 
a DHCPRELEASE, it is still fatal, because the lease file may contain a 
lease indicating that the IP address is owned by the client, and DHCPRELEASE 
is a relinquishment of ownership of the lease.   But this shouldn't be 
a problem in the case you're talking about. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.