00:16:39 rmustacc: re: the heads-up ==> ship it. 00:27:01 I think I have a grip on what it will take to migrate SMF to sqlite3. I've started writing an IPD to discuss some of the options (not quite ready to circulate). 00:37:23 Early in boot, the repository database can ping-pong back and forth between /etc/svc/repository.db and /etc/svc/volatile/fast_repository.db to enable early manifest import and r/w smf db access before root is r/w. so we could potentially build a conversion tool run by svc.startd early in boot which creates a sqlite3 version in /etc/svc/volatile from the sqlite2 database in /etc/svc/repository.db before starting a sqlite3-only svc.configd. 00:39:54 danmcd: looks like I missed pgrep/pkill(1) when I added history sections to most of the other proc tool man pages in https://gist.github.com/alanc/9bb7337ee5e6a2aa641a6a0e5b0d8901 but looking in the old teamware gates, the first to have pgrep/pkill is on998-gate, aka S7 00:42:01 Wow... thank you for that. Given you pasted this here on IRC, I may share this link with others. 00:44:06 I've shared the link on twitter before, and possibly even here 00:45:16 Even better then (and sorry for missing those earlier ones). 00:45:36 It's certainly not secret - any user with the boot environments for the two SRU's could generate the diff - I just share those each quarter so people can more easily see the changes in the man pages they might not notice on their own 00:47:12 https://gist.github.com/alanc has a them for a bunch of prior quarterly feature releases too 00:48:33 I know it makes rich sad that I can't put them under any license other than "Feel free to read these" so you can't just apply the diffs 01:09:07 (Makes me sad too, FTR, but I understand.) 17:33:36 https://github.com/illumos/illumos-gate/blob/master/usr/src/lib/libdladm/common/libdlaggr.c#L539-L544 <-- I don't see any way this can be called without DLADM_OPT_ACTIVE set, so this seems superfluous 17:47:03 toasterson: also check MTU between connect server/client 17:48:07 igork: I managed to fix it. it was a missing ipfilter package in the zone. Dependency entries are missing, bug is opened for that 17:49:11 toasterson: yes, nfs service depend on ipfilter binaries and service 17:53:06 igork no, nfs/server does not depend on ipfilter (nor should it). 17:53:47 danmcd: unfortunately it has to otherwise it goes to maintenance with a svcprop command failing 17:53:58 milestone/network *does* apparently, and that blocks nfs/server. 17:54:34 danmcd: take a look nfs server service - /lib/svc/method/nfs-server 17:55:02 # Handling a corner case here. If we were in offline state due to an 17:55:03 # unsatisfied dependency, the ipf_method process wouldn't have generated 17:55:03 # the ipfilter configuration. When we transition to online because the 17:55:03 # dependency is satisfied, the start method will have to generate the 17:55:03 # ipfilter configuration. To avoid all possible deadlock scenarios, 17:55:03 # we restart ipfilter which will regenerate the ipfilter configuration 17:55:03 # for the entire system. 17:55:20 and also 17:55:23 . /lib/svc/share/ipf_include.sh 17:55:36 i'm not crazy :) 17:55:47 probably a little ? :) 18:01:18 there is also an svcprop call in there which looks for ipfilter service see #15560 19:04:24 tsoome: can you ping me when you need another pass through NFS? 19:46:49 sure 19:52:55 thanks 21:24:07 [illumos-gate] 15553 dlmgmtd asserts on processing NGZ persistent configuration file -- Andy Fiddaman 21:37:53 [illumos-gate] 14577 ESX offline disk resize prevents growing zpool -- Jason King