Date: Tue, 10 Oct 2017 23:25:14 +0200 From: "Kristof Provost" <kristof@sigsegv.be> To: "Oleg Ginzburg" <olevole@olevole.ru> Cc: "FreeBSD Current" <freebsd-current@freebsd.org>, "Goran =?utf-8?q?Meki=C4=87?=" <meka@tilda.center>, freebsd-jail@freebsd.org Subject: Re: VNET jail and dhclient Message-ID: <6BA6DE01-9D89-4790-99CD-73485722BF14@sigsegv.be> In-Reply-To: <CAMsb%2BmaactJTDcK=j%2BawqkXB6YitQ_dQTp9vvs=a%2BTFjrQTA7w@mail.gmail.com> References: <20171009072547.jauim6tlfennydf5@hal9000.meka.no-ip.org> <6D37D4AC-9DF4-4D55-8614-43CFC6BDD45E@sigsegv.be> <CAMsb%2BmaactJTDcK=j%2BawqkXB6YitQ_dQTp9vvs=a%2BTFjrQTA7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10 Oct 2017, at 23:10, Oleg Ginzburg wrote: > What is your FreeBSD version? This problem reproduced on FreeBSD 12 > only. > /var/empty is exist and trivial test: > I’m running r324317 on CURRENT, yes. What arguments are you calling dhclient with? Clearly there’s a difference between what you’re doing and what I’m doing. > I'm not sure if this fd leak (due to pidfile_remove at the end of > dhclient), nevertheless closing pid fd in my jail/FreeBSD12 before > chroot > solve dhclient issue. I would not expect an open file descriptor to be a problem, unless perhaps you’ve got an open directory and kern.chroot_allow_open_directories is unset. Regards, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6BA6DE01-9D89-4790-99CD-73485722BF14>