Re: New procps release soon

On 9/24/24 7:10 AM, Craig Small (csmall) wrote:
> I've basically ran vmstat in a loop on a lxc container all day testing 
> for non-zero exit result and it works.
> 
> There's something specific about Jim's and Debian CI containers that 
> cause this.
> blem
> There's scarce information except it gives no output and non zero exit 
> which is a very odd thing in itself.

Hi Craig,

I should have provided more information in my earlier reply.

When I can (inconsistently) reproduce the vmstat problem, it's following 
a build without --disable-shared and a 'sudo make install'.  So I was 
running vmstat from /usr/local/bin and /usr/local/lib still relied on 
that darn libtool libproc2.la script.

I don't pretend to understand the libtool inner workings but these lines 
in that script caught my eye:

     # Is this an already installed library?
     installed=yes

My distro is using procps-ng v4.0.4 where the maximum meminfo item 
enumerator is valued at 131.  Eight more items have been added since.

The vmstat program uses, among others, MEMINFO_SWAP_USED.  In our git 
repo currently, that guy is assigned a value of 135.

So, if vmstat was compiled against the current HEAD but somehow linked 
against the v4.0.4 library, that could explain a failure of his 
procps_meminfo_select() call.

Just a thought.

Regards,

Jim