00:12:58 I think you have to go back to SunOS 4 or so to be able to get right into single-user mode with no password 00:19:36 richlowe: I feel like if you "boot -a" it _asks_ you where /sbin/init is 00:46:02 [illumos-gate] 16222 TSC vmware calibration could be more general -- Patrick Mooney 01:00:04 hello all, what’s the dtrace command or script can be used to generate ZFS call stack and used to check the performance, like this https://rfd.shared.oxide.computer/rfd/image/490/flamegraph.png , anyone could share me the script or command? thank you very much, I’m going to check if ZFS had performance issue with postgres, best wishes 01:19:54 tozhu: I assume that one was generated by the "flamegraph" command, which is written in Rust. I know Matt Keeter (who I believe wrote the RFD you're looking at there) has been working on it, e.g., https://github.com/flamegraph-rs/flamegraph/pull/334 01:41:10 jclulow: thank you, flamegraph command used to generate the picture, I need the script used to generate the data which used to generate the picture, thank you 01:41:35 tozhu: I believe that program can also drive DTrace to get the data 01:45:15 jclulow, thank you very much for the advice, I’ll take a look, thank you 01:51:11 jclulow: the tool is really cool, thank you, and thanks for Matt Keeter 01:51:23 Excellent! 07:06:34 There is also https://github.com/brendangregg/FlameGraph.git -- it does provide many samples about data collecting and other bits. 10:51:15 tsoome_ thank you very much 11:19:03 yw 11:20:00 I have found that the hardest part is to target the data gathering to the moment you actually need to profile :D 21:14:48 [illumos-gate] 15488 libbsm: storing the address of local variable -- Toomas Soome 21:19:36 .oO slowly getting to more recent gcc :P 21:31:41 the only way to do it, is either have a block of free time, or to pick a version and _stick to it_ 21:31:47 even if people complain that N+1 is now available 21:32:17 I don't believe illumos is at a place we can ever actually catch up in one leap 21:32:22 xeno's paradox, etc. 21:33:20 (but there're also all the quality fixes that attempting it brings in...) 23:42:06 currently, if you fail to set NIGHTLY_OPTIONS in the environment file, nightly fails with a usage error, in a somewhat roundabout way. 23:43:56 (you get a usr/src/tools/scripts/nightly: -a: unknown option error first) 23:44:37 because it defaults NIGHTLY_OPTIONS to "-aBm" if it is unset after the environment file. 23:45:12 and -a went away in 78add226e8da271dde8f3b5a91d340d1bf010151 in 2010 23:46:05 (-a was used to create BFU archives) 23:49:01 so I'm running with richlowe's suggestion to add a few command line options to nightly (to set CODEMGR_WS and BRINGOVER_WS) and noticed this oddity when searching for option letters to use. 23:55:41 [illumos-gate] 16734 ktest is not i386 specific -- Richard Lowe 23:59:59 so I could fix it by changing to a safe default (B is an undocumented flag that is treated as equivalent to D, so "-Dmn") or else have it just spit out the usage message.