On Tue, Dec 12, 2017 at 11:56:20AM +0000, Stuart Henderson wrote: > Quick thought (I don't have time to look further now but I just noticed > this and wanted to get it down before I forget). > > I just upgraded an Alix to 6.2 release and then wanted to run syspatch > afterwards. I logged in just after ssh had started, so reorder_kernel was > still running in the background - it didn't finish until uptime=8 mins. > > It's not going to be a problem for systems with faster storage, but there are > likely still plenty of machines like this around just plodding along. Thinking > about users who may not realise about the background reorder_kernel, is this > enough of a problem to be worth adding some kind of interlock to prevent > syspatch from running before reorder_kernel finished?
I suppose I could add such a check if we want it. -- Antoine
