Date: Sun, 12 Sep 2010 13:00:12 +0900 From: Norikatsu Shigemura <nork@FreeBSD.org> To: Wesley Shields <wxs@freebsd.org>, jpaetzel@freebsd.org Cc: ports@freebsd.org, Tetcu <itetcu@freebsd.org>, Ion-Mihai, Norikatsu Shigemura <nork@freebsd.org>, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons Message-ID: <20100912130012.ce7e44cc.nork@FreeBSD.org> In-Reply-To: <20100912002156.GA995@icarus.home.lan> References: <20100911222902.bb57444a.nork@FreeBSD.org> <20100911173359.68d71af6@it.buh.tecnik93.com> <20100912000928.GA9073@atarininja.org> <20100912002156.GA995@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi everyone! Thank you for my reply. This problem is 'Yet another minor release engineering' for all the world other environments. If you can give assurance upgrading ports, you can stop the daemon (at least, I want to restart it:-). But it's toooooooo difficult, and I(we?) don't/can't want your assurance. If the daemon doesn't stop (keep the daemon running), I(we) am given a little grace to update environment like configuration files. If the daemon stop, I(we) should correspond updating at once. In theoretically, we update ports like following operation: 1. Check updating lists like portversion -L =. 2. Check updating documents before portupgrade XXX. 3. portupgrade every once, and update environments (including restart OS). 4. repeat 3. But it's hard, so in practice: 1. portupgrade -aR. 2. Check updating documents, and update environments. 3. repeat 3. 4. restart OS if needed. So please regard such as system managers! -- Norikatsu Shigemura <nork@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100912130012.ce7e44cc.nork>