Date: Tue, 17 Aug 2010 10:17:23 +0200 From: Beat Siegenthaler <beat.siegenthaler@beatsnet.com> To: freebsd-questions@freebsd.org Subject: Re: Upgrading ports while processes are running. Message-ID: <4C6A4593.8030405@beatsnet.com> In-Reply-To: <84y6c6rnpp.fsf@shroyer.name> References: <4C69D13F.9080404@dannysplace.net> <20100817032327.0349772b.freebsd@edvax.de> <84y6c6rnpp.fsf@shroyer.name>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17.08.10 04:13, Mark Shroyer wrote: > That isn't to say you won't see any negative consequences from > overwriting a running port with a newer version. Hypothetically, you > might install a new Python including a new standard library, and if your > running (old) Python process tries to load one of its deleted modules > from disk something could break. Or not; I'm no expert on the ports > system, they might have some way of working around this. But as for a > pragmatic answer to your question, I err on the side of caution with > this stuff Wow, thanks for this perfect description how this is working. For my part, I am updating since many years regularly the ports. Never stop any daemon before. But after the upgrade I restart the daemon if it is something like apache, clamav, some milters, mysql. It never causes trouble. The only thing that if I use restart, rc says the daemon is not running (but running fine) . But after reading Your article it is now clear why. Beat
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C6A4593.8030405>