01:01:06 <alanc> https://github.com/esnet/iperf/pull/2071 may help on illumos too
01:07:29 <danmcd> Thank you @alanc.
01:24:54 <Guest83> hi
02:14:26 <Smithx10> 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  
06:29:27 <tsoome> Smithx10 like smbios command?
07:20:17 <carba> @danmcd: I added some tests to #18324, I cannot reply to the RTI message at illumos-advocates.
07:32:13 <Agnar> Smithx10: smbios might help. but yes, there is a long tradition of writing wrapper scripts for prtdiag ;)
07:55:42 <wiedi> https://github.com/TritonDataCenter/hwgrok/
07:59:14 <Agnar> oh nice
11:38:01 <Smithx10> wiedi:  you use that recently?
11:38:21 <wiedi> no, been a while. Is it broken?
11:39:24 <Smithx10> I just saw the date and I got scurred 
11:39:58 <Smithx10> i'll give it a go later after 4 cups of coffee when I get courage
11:40:18 <wiedi> :)
11:44:13 <Agnar> I just built it on amd64 and seems the 64bit version works now
11:45:04 <Agnar> 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. 
12:58:12 <danmcd> THanks @carba have a meeting, will followup after.
14:03:15 <jbk> hrm.. i tried it (forgot about it) on dell running omni and walking the topo snapshot is failing (yet fmtopo works)
14:03:53 <jbk> 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)
14:06:10 <Agnar> for all amd64 machines, prtdiag will look the same...if that helps
14:08:41 <Agnar> ah, just ran fmtopo here and hwgrok and fmtopo - of course as both use libtopo - lack the same data
14:09:44 <jbk> 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)...
14:10:20 <jbk> (i'd like to write down as much as I understand on it -- though it's almost certianly incomplete.. just so there is something)
14:12:29 <Agnar> do you use ansible by any chance?
14:12:35 <jbk> no
14:13:07 <Agnar> ok, that could have been an option also - it has a module called "setup" that collects a bunch of data about systems it manages
14:13:21 <Agnar> but I may have a shell script for you as well...give me a minute
14:20:54 <Agnar> jbk: maybe this can be helpful: https://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.
14:21:15 <Agnar> jbk: if it is useful for you and you have questions: olbohlen⊙ed :)
14:32:35 <neirac> I tried  https://src.illumos.org/source/ but I'm getting a 502, maybe is just me?
14:33:35 <Agnar> neirac: no, same for me.
14:48:34 <Smithx10> I was hoping to be able to extract this information and sync it into a DCIM.   
14:59:24 <danmcd> carba: Approved.  Will push sometime today. (Both home and work are spinning wildly so pardon latency & jitter.)
17:39:55 <gitomat> [illumos-gate] 18371 wrong sigset_t size with ucontext.h first and XPG4v2 on amd64 -- Gordon Ross <gordon.w.ross⊙gc>
17:39:55 <gitomat> [illumos-gate] 18293 Program including ucontext.h does not build -- Gordon Ross <gordon.w.ross⊙gc>
17:39:55 <gitomat> [illumos-gate] 18294 POSIX Program including ucontext.h does not build -- Gordon Ross <gordon.w.ross⊙gc>
18:02:36 <gitomat> [illumos-gate] 18322 virtio: add support for VIRTIO_F_RING_EVENT_IDX -- Andy Fiddaman <illumos⊙fn>
18:22:39 <gitomat> [illumos-gate] 18324 Remove the old notes section from core file -- Carsten Grzemba <cgrzemba⊙oo>
19:56:25 <richlowe> danmcd: we need to work out what the state of my outstanding RTIs is
19:56:38 <richlowe> I say "we" because they're mine, but I... don't know? I think they were approved and we're good now?
19:56:41 <richlowe> maybe you were going to check them?
19:59:18 <gitomat> [illumos-gate] 17903 loader: expose addresses of firmware tables in loader env -- Toomas Soome <tsoome⊙mc>
20:02:59 <danmcd> 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.
21:00:51 <richlowe> (also, this desync was my fault, not Dan's)