esnet/iperf #2071 may help on illumos too

Thank you @alanc.

hi

Are there any utilities that can make it simple to parse basic hardware information? Trying to get vendor / model number / part number programmatically.... this isn't that easy lol

Smithx10 like smbios command?

@danmcd: I added some tests to #18324, I cannot reply to the RTI message at illumos-advocates.

Smithx10: smbios might help. but yes, there is a long tradition of writing wrapper scripts for prtdiag ;)

oh nice

wiedi: you use that recently?

no, been a while. Is it broken?

I just saw the date and I got scurred

i'll give it a go later after 4 cups of coffee when I get courage

:)

I just built it on amd64 and seems the 64bit version works now

however...I miss some data that prtdiag/smbios have - for example it doesn't detect my system as a DELL laptop, which the other tools do.

THanks @carba have a meeting, will followup after.

hrm.. i tried it (forgot about it) on dell running omni and walking the topo snapshot is failing (yet fmtopo works)

because $BOSS has been asking about getting something that gives a hw inventory of a system, and this would be a good starting point (if not complete solution)

for all amd64 machines, prtdiag will look the same...if that helps

ah, just ran fmtopo here and hwgrok and fmtopo - of course as both use libtopo - lack the same data

might need a custom topo map.. unfortunately there's not much in the way of docs on how to do that (other than look at existing ones and the source)...

(i'd like to write down as much as I understand on it -- though it's almost certianly incomplete.. just so there is something)

do you use ansible by any chance?

no

ok, that could have been an option also - it has a module called "setup" that collects a bunch of data about systems it manages

but I may have a shell script for you as well...give me a minute

jbk: maybe this can be helpful: eenfach.de/~olbohlen/datacollector.ksh I wrote it almost 13 years ago, it runs on Solaris/illumos/Linux(Suse,Redhat) and produces CSV files for various aspects on the systems.

jbk: if it is useful for you and you have questions: olbohlen⊙ed :)

I tried src.illumos.org/source but I'm getting a 502, maybe is just me?

neirac: no, same for me.

I was hoping to be able to extract this information and sync it into a DCIM.

carba: Approved. Will push sometime today. (Both home and work are spinning wildly so pardon latency & jitter.)

[illumos-gate] 18371 wrong sigset_t size with ucontext.h first and XPG4v2 on amd64 -- Gordon Ross <gordon.w.ross⊙gc>

[illumos-gate] 18293 Program including ucontext.h does not build -- Gordon Ross <gordon.w.ross⊙gc>

[illumos-gate] 18294 POSIX Program including ucontext.h does not build -- Gordon Ross <gordon.w.ross⊙gc>

[illumos-gate] 18322 virtio: add support for VIRTIO_F_RING_EVENT_IDX -- Andy Fiddaman <illumos⊙fn>

[illumos-gate] 18324 Remove the old notes section from core file -- Carsten Grzemba <cgrzemba⊙oo>

danmcd: we need to work out what the state of my outstanding RTIs is

I say "we" because they're mine, but I... don't know? I think they were approved and we're good now?

maybe you were going to check them?

[illumos-gate] 17903 loader: expose addresses of firmware tables in loader env -- Toomas Soome <tsoome⊙mc>

We have discussed this in DM, wider audience, and I will be looking at it tomorrow with the intention of pushing unless something HORRID surfaces.

(also, this desync was my fault, not Dan's)