Date: Mon, 26 Apr 1999 15:51:53 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Spidey <beaupran@jsp.umontreal.ca> Cc: freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Bind in a sandbox Message-ID: <Pine.BSF.4.03.9904261551060.6951-100000@resnet.uoregon.edu> In-Reply-To: <Pine.BSF.3.96.990424142257.3828A-100000@freed.dyn.ez-ip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Apr 1999, Spidey wrote: > Hi! > > I've been running BIND in a sandbox for some time now. I have a > intermittent connection to the net, so sometimes, I have messages like > named[$$]: deleting interface $MYADDR.53. This was normal. > > But now that I run BIND in a sandbox, I get: > > Apr 24 14:22:25 freed named[101]: bind(dfd=22, [10.0.2.15].53): > Permission denied > Apr 24 14:22:25 freed named[101]: bind(dfd=22, [10.0.2.15].53): Permission > denied > Apr 24 14:22:25 freed named[101]: bind(dfd=22, [10.0.2.15].53): Permission > denied > Apr 24 14:22:25 freed named[101]: deleting interface [10.0.2.15].53 > > > I start bind using: named -u bind -g bind > > Thanks. Since you're not running as root, you're not allowed to attach to the privilieged port 53. I'm not familiar with the sandbox behavior so I don'tknow how named gets around this. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9904261551060.6951-100000>