On Wed, Oct 03, 2018 at 10:01:58PM +0200, Christoph Berg wrote: > It is parsing the `free` output to probe available memory. The code is > utterly wrong since free had been changed to output only two lines > instead of three, so it looks at the amount of swap available. I > haven't checked, but my guess is that on systems without swap, you'll > get the above error.
I confirm that the system where it fails lacks swap and that my local system where it succeeds does have swap. Your hypothesis fully matches my observations. Helmut
