Date: Sun, 12 Nov 2017 20:34:05 +0100 From: Michael Grimm <trashcan@ellael.org> To: freebsd-jail@FreeBSD.org Subject: Re: Update jails strategy Message-ID: <5D52F06D-7264-4F28-88D7-CEC0A18769FA@ellael.org> In-Reply-To: <5A083779.6070509@quip.cz> References: <8A68CBC6-16B0-494F-ACA4-B46404E49362@ellael.org> <5A083779.6070509@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Miroslav Lachman <000.fbsd@quip.cz> wrote: > Michael Grimm wrote on 2017/11/11 21:42: >> [FYI: I am running some service jails with an ezjail-type basejail = approach.] >>=20 >> Until now I did stop all jails before updating and restarting them = afterwards. Now I am wondering if that is necessary at all. >>=20 >> Wouldn't it be sufficient to update basejail with running jails and = restart them after this updating? (In analogy to a "make installworld; = make installkernel; reboot") >=20 > Update of basejail and restart of jails is enough. I am doing it this = way for a years. Thanks, that's what I wanted to hear ;-) > We have build server with prepared updates mounted thru NFS and then = just make installkernel && make installworld (+ mergemaster) in host = system. After the host is updated (before reboot) I run my local script = to rsync changes from host to basejail (sync just bin, sbin, libs, but = not home, etc, var), then mergemaster in all jails and finally reboot = the server. I never stop jails before update. Ok. Until now I did something similar: #) make buildworld && make buildkernel at fastest server #) zfs send /usr/obj and /usr/src to remote server #) make installworld && make installkernel at remote server I did use "ezjail-admin update" to update basejail only after stopping = all jails. That I will omit from now on, thanks. Regards, Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D52F06D-7264-4F28-88D7-CEC0A18769FA>