Date: Wed, 15 Sep 2010 00:19:43 -0700 From: perryh@pluto.rain.com To: dougb@freebsd.org Cc: ports@freebsd.org, swhetzel@gmail.com, itetcu@freebsd.org, nork@freebsd.org Subject: Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons Message-ID: <4c90738f.W4uzxD1k7guRTp%2Bn%perryh@pluto.rain.com> In-Reply-To: <4C901FD0.5000304@FreeBSD.org> References: <20100911222902.bb57444a.nork@FreeBSD.org> <20100911173359.68d71af6@it.buh.tecnik93.com> <AANLkTin0D13%2B9JQJ6wVD7_48Es6rvUJtu=rAx6M1xdjx@mail.gmail.com> <4C901FD0.5000304@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton <dougb@freebsd.org> wrote: > >>> ... Is it really absolutely necessary > >>> to stop a service before it's files go away? > > IMO the only time the ports infrastructure itself should do this > is if it isn't possible to pkg_delete the port cleanly if it's > running. For example, if there is a file being held open that > cannot be deleted unless the service is stopped ... Which should be an exceedingly rare circumstance, since the fact of some process(es) having a file open will not ordinarily prevent the removal of any or all directory entries pointing to it. The inode and disk space won't actually be released until the last such process closes the file, but another file could be created having the same pathname as the one whose prior directory entry was removed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4c90738f.W4uzxD1k7guRTp%2Bn%perryh>