On Mon, Aug 30, 2021 at 11:11:55AM +0200, Martin Pieuchot wrote:
> On 13/07/21(Tue) 00:55, Anindya Mukherjee wrote:
> > On Sat, Jul 03, 2021 at 11:20:42AM +0100, Stuart Henderson wrote:
> > > On 2021/07/03 01:09, Anindya Mukherjee wrote:
> > > > Thanks for the
Many thanks!
Anindya
On Sat, Aug 14, 2021 at 08:22:45AM -0600, Todd C. Miller wrote:
> On Wed, 28 Jul 2021 12:13:23 -0700, Anindya Mukherjee wrote:
>
> > While running systat(1)'s iostat view in cumulative mode (activated by
> > pressi
> > ng
> > 'b&#x
ping
On Fri, Aug 06, 2021 at 02:34:07PM -0700, Anindya Mukherjee wrote:
> ping
>
> > Hi,
> >
> > While running systat(1)'s iostat view in cumulative mode (activated by
> > pressing
> > 'b') I noticed that it divides the results by the refres
ping
> Hi,
>
> While running systat(1)'s iostat view in cumulative mode (activated by
> pressing
> 'b') I noticed that it divides the results by the refresh interval. This is
> because the cumulative mode is implemented by setting last = 0, and then it
> does
> (current - last) / etime, thereby
Hi,
While running systat(1)'s iostat view in cumulative mode (activated by pressing
'b') I noticed that it divides the results by the refresh interval. This is
because the cumulative mode is implemented by setting last = 0, and then it does
(current - last) / etime, thereby giving wrong cumulative
tuart Henderson wrote:
> On 2021/07/03 01:09, Anindya Mukherjee wrote:
> > Thanks for the discussion. This has been very illuminating. I have been
> > digging
> > around in /usr/src/ and ignoring the atomic architectures (where I got
> > stuck) it
> > looks like it should
On Sat, Jul 03, 2021 at 11:20:42AM +0100, Stuart Henderson wrote:
> On 2021/07/03 01:09, Anindya Mukherjee wrote:
> > Thanks for the discussion. This has been very illuminating. I have been
> > digging
> > around in /usr/src/ and ignoring the atomic architectures (where
, 2021 at 11:20:42AM +0100, Stuart Henderson wrote:
> On 2021/07/03 01:09, Anindya Mukherjee wrote:
> > Thanks for the discussion. This has been very illuminating. I have been
> > digging
> > around in /usr/src/ and ignoring the atomic architectures (where I got
> > stuck)
Thanks for the discussion. This has been very illuminating. I have been digging
around in /usr/src/ and ignoring the atomic architectures (where I got stuck) it
looks like it should be possible to use uint64_t everywhere. I'm playing with
some changes on my machine to see if I can get at least syst
Hi,
I noticed that if I leave the system running for more than about a month, some
of the counters in the uvm view of systat(1) overflow and become negative. This
is because the members of struct uvmexp in sys/uvm/uvmexp.h are ints. The
kernel's internal counters are of course uint64_t so they don
ead of claiming another binding, why not make help, order
> and view a toggle? I see no reason why this information should disappear
> on the next input.
>
> Seems to work fine in my testing.
>
> OK?
>
> martijn@
>
> On Thu, 2021-03-04 at 22:47 -0800, Anindya Mukherjee wro
On Sat, May 08, 2021 at 07:26:32AM +0200, Sebastien Marie wrote:
> On Thu, May 06, 2021 at 06:23:08PM -0700, Anindya Mukherjee wrote:
> > On Thu, May 06, 2021 at 08:00:56AM -0600, Todd C. Miller wrote:
> > > On Thu, 06 May 2021 09:32:28 +0200, Sebastien Marie wrote:
> > &g
On Thu, May 06, 2021 at 08:00:56AM -0600, Todd C. Miller wrote:
> On Thu, 06 May 2021 09:32:28 +0200, Sebastien Marie wrote:
>
> > We already take care of such situation with __cxa_thread_atexit_impl
> > (in libc/stdlib/thread_atexit.c), by keeping an additionnal reference
> > on object loaded (it
On Thu, May 06, 2021 at 08:00:56AM -0600, Todd C. Miller wrote:
> On Thu, 06 May 2021 09:32:28 +0200, Sebastien Marie wrote:
>
> > We already take care of such situation with __cxa_thread_atexit_impl
> > (in libc/stdlib/thread_atexit.c), by keeping an additionnal reference
> > on object loaded (it
Ic ^V | Aq Ic Page Down
Scroll current view down by one page.
.It Ic Alt-V | Aq Ic Page Up
On Mon, Mar 01, 2021 at 08:37:58AM +0100, Martijn van Duren wrote:
> On Sun, 2021-02-28 at 23:03 -0800, Anindya Mukherjee wrote:
> > Hi,
> >
> > Thanks for the feedback. I see
y: h, which also displays help, which if I come from
> ^G is not what I want and if I'm in help is confusing, because I want
> to get rid of it.
>
> martijn@
>
> On Sun, 2021-02-28 at 19:40 -0800, Anindya Mukherjee wrote:
> > Hi,
> >
> > I tend
Hi,
I tend to keep systat(1) running in interactive mode, and find it very
useful to have the help line displayed permanently, i.e., not disappear
if a key is pressed or after a command is executed. The same goes for
the Ctrl-G display. For example, it tells me what modes are adjacent to
the curre
Thanks! This works perfectly!
On Sun, Feb 28, 2021 at 12:01:06AM +0100, Theo Buehler wrote:
> > Following the advice in the FAQ I added my user to the wobj group. I
> > suppose I could "make obj" and have the objs written to /usr/obj? Is
> > this a workflow the developers recommend or follow? Than
Hi,
I am making a small change to systat(1) and hope to submit it for review
soon. For my own edification, I have a few questions regarding the
recommended workflow for such work. Hopefully tech@ is the right place
to ask this :)
I generated the tags with "make tags", and also temporarily added -
Hi,
I have been noticing this leak for a few weeks now. I typically update
to the latest snapshot every 10-14 days and Xorg memory usage grows
monotonically in the meantime. I was gathering some data for a report,
but thanks to this thread it's explained now. I look forward to testing
the fix. I a
2bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0
wskbd1: connecting to wsdisplay0
wskbd2: connecting to wsdisplay0
wskbd3: connecting to wsdisplay0
wskbd4: connecting to wsdisplay0
wskbd5: connecting to wsdisplay0
wsdisplay0: screen 1-5 added (std, vt100 emulati
(std, vt100 emulation), using wskbd0
wskbd1: connecting to wsdisplay0
wskbd2: connecting to wsdisplay0
wskbd3: connecting to wsdisplay0
wskbd4: connecting to wsdisplay0
wskbd5: connecting to wsdisplay0
wsdisplay0: screen 1-5 added (std, vt100 emulation)
On Tue, Feb 09, 2021 at 08:34:00AM +0100, An
On Tue, Feb 09, 2021 at 08:34:00AM +0100, Anton Lindqvist wrote:
> Hi,
>
> On Mon, Feb 08, 2021 at 02:50:39PM -0800, Anindya Mukherjee wrote:
> > Hi, I have a Logitech M570 which seems to be handled by this new driver.
> > However I don't see any battery level i
Hi, I have a Logitech M570 which seems to be handled by this new driver.
However I don't see any battery level information.
dmesg:
uhidpp0 at uhidev4 device 1 mouse "M570" serial ef-81-ff-80
sysctl kern.version:
kern.version=OpenBSD 6.8-current (GENERIC.MP) #313: Fri Feb 5 18:31:44 MST 2021
24 matches
Mail list logo
