DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 26370385EC3F
MIME-Version: 1.0
References: <CAN0SSYxv9A8V6gGppEid0LnjHJtY4isDUFY-ey=nbM9PaDo_8g AT mail DOT gmail DOT com>
 <be924247-c927-4fd7-8673-3cab4172aae7 AT dronecode DOT org DOT uk>
 <2225cf8a-cb8a-6437-177d-9a83f7dec53c AT cs DOT umass DOT edu>
In-Reply-To: <2225cf8a-cb8a-6437-177d-9a83f7dec53c@cs.umass.edu>
Date: Tue, 27 Aug 2024 22:49:57 +0200
Message-ID: <CAKAoaQkCZS+HW5Rk6_qNxNA66FPgzwy2gVOYZGkiGPzBQ9VY5A@mail.gmail.com>
Subject: Re: BUG: /usr/bin/uptime always reports 0/0/0 average
To: cygwin AT cygwin DOT com
From: Roland Mainz via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Roland Mainz <roland DOT mainz AT nrubsig DOT org>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

On Tue, Aug 27, 2024 at 6:29 PM Eliot Moss via Cygwin <cygwin AT cygwin DOT com> wrote:
> On 8/27/2024 11:31 AM, Jon Turney via Cygwin wrote:
> > On 27/08/2024 09:21, Mark Liam Brown via Cygwin wrote:
> >> Greetings!
> >>
> >> /usr/bin/uptime always reports 0/0/0 average cpu load:
> >> $ uptime
> >>   10:09:01 up 15:59,  0 user,  load average: 0.00, 0.00, 0.00
> >>
> >> is this a known bug?
> >
> > Kind of.
> >
> > Due to windows API limitations, the current implementation has the short-coming that a process's first call to
> > getloadavg() does not update the globally-maintained loadavg data.
> >
> > (Because the Windows API cannot provide instantaneous cpu load, only over the period between two calls)
> >
> > (So e.g. if you run something like top in another terminal, you'll suddenly see uptime return more sensible values)
> >
> > See the discussion [1] for more context, and discussion of various approaches to fixing this, which petered out without
> > a patch to [2]...
> >
> > [1] https://cygwin.com/pipermail/cygwin-developers/2022-May/012569.html
> > [2] https://cygwin.com/cgit/newlib-cygwin/tree/winsup/cygwin/loadavg.cc
>
> Thank you for the explanation, Mark!
>
> I see that /proc/loadavg appears to get updated.  If one wants the information,
> is that a more reliable source than calling uptime for load averages?

What about adding a new cygwin daemon, or add a loadavg-thread to cygserver ?

----

Bye,
Roland
-- 
  __ .  . __
 (o.\ \/ /.o) roland DOT mainz AT nrubsig DOT org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple