Is there any support for io_uring in linuxlator?

looks nice V_PauAmma_V

are all of the 'page' category infos in man vmstat referring to swap paging? like even flt/page faults?

in vmstat procs section, what does b mean? man page says blocked for resources, so does that mean the process wants to run but can't because another part of the system is bogged down?

i wonder if w could also be updated to avoid cursed hacks like env LC_TIME=de_DE.ISO8859-15 uptime

while this is like adding hell to hell:

env LANG=de_DE.ISO8859-15 uptime --libxo=json

"load-average-15": 0,47

endless joy

i'm surprised xo even outputs that

but it's piece-oriented lib and it outputs whatever you wish

i recall ps just went 24h clock

i guess noone complained either about ps being in "military" time

i can recall number of times the locales and charsets making my life hell :p

so i take it there's no way to make vmstat not repeat the headings every page or so? linux vmstat has an option for that why do we always get left out

kerneldove: i wonder what's exec overhead

vmstat queries the kernel

so if vmstat is cached already

dunno?

but broken json is bug

i bet if you are streaming vmstat every 1s then it should be looped within that program

yeah i don't know what's overhead of executing binary

i don't even know how it works actually

all the hardware and internals are too hard to learn

somehow

also where's that stats going?

i'm running vmstat once then parsing its output. just too bad i now have to detect when it's randomly a heading line instead of another data line. linux vmstat doesn't have that problem

that's some test setup?

system monitoring

i'm ingesting everything significant the collating it in my mgmt platform

every second?

nah

every 15s

still high, what's the usecase?

it's fast changing data for sure but

optimize workload. basically trying to get every drop of perf out of hardware i can

hmm

ya 15s is as frequent as i'll go. might up it to 60s, but for now 15 is where i'll start

what are those machines doing?

running network services

i wonder if i'm able to fix xo on my own

there

i bet you can

i was looking at the vmstat.c today

but i hate that style

cgit.freebsd.org/src/tree/usr.bin/vmstat/vmstat.c#n756 see that?

if library functions are built like that, no wonder dev can't see what (s)he's doing

oh god

why did i even look

if you detect that multiple displays will take place, then above that line you run xo_open_container("display");, and same for close at end of the set of display objs

you don't know c?

more like xo book is missing in my head

more than c book

xo_close_container("processes"); xo_close_container("vmstat");

missing after a loop

and it needs to start again

basically you can fix it by

changing things so it works if runs==1

or runs==inf

i don't see where this even starts

but somewhere it does

if you do it all, both single and multi runs are correct

how about we move xo open con cmstat into dovmstat

and close too

wait it's wrong

but vmstat open/close is in main() and that's bad

if (reps > 1) { xo_close_container("vmstat"); xo_open_container("vmstat"); }

i hate it all

dointr needs it too

i can't understand anything anymore

why not?

somewhere there whole vmstat needs to close and reopen

how, no idea

and text mode needs to stay functional too

start by wrapping the display set in a "display" open and close container. then add a gate around those containers based on whether or not there's gonna be multiple displays

text mode runs headers every screenful

yeah but i'm already tired of that

oh and if you that, everyone's parser breaks

if (reps >= 0 && --reps <= 0) break;

here loop breaks if only one run

maybe put else here to repeat the close open

i bet everything that uses xo is filled with such bugs

it was simply missed that in loop, it can print the middle part again

and if somebody uses vmstat 1 --libxo=json

this fix breaks their parser hack

oh and how to fix the padding without breaking text?

maybe i would be better at putting -s into w.c while it's argv0==uptime

sadly w once had -s

or i can keep doing variant of time="`date +%s`"; boottime="`sysctl -n kern.boottime | cut -d , -f 1 | cut -d ' ' -f 4`"; uptime="$(($time - $boottime))"

ketas: w was imported back in 1994 with '-s is no longer supported'

so i wouldn't say it did ever :)

what did that ever do?

no idea

before 94

Look like after deep search that even shrinking methods is impossible in my situation :(

Only solution is having a third hard drive to dump /, then recreate the partition smaller, I will do it when I connect my drive

In april; bec. the next months I will be so busy

what's the proper way to UEFI boot FreeBSD UNIX v14.3 with GRUB v2 either specifying everything or chainloading? Lately when I chainload, I see graphical FreeBSD boot-loader but then after pressing <ENTER|RETURN> and a second or two it just always reboots

it had installed okay, and I thought I was able to do this before. I've booted the installation before