17:02:55 <gitomat> [illumos-gate] 3409 mdb: Open source implementation of nfs module -- Vitaliy Gusev <gusev.vitaliy⊙gc>
17:16:13 <tsoome> whee:)
17:20:02 <danmcd> Thanks for your patience.  Big upstream things like this benefit from documentation and stories of time-in-the-field.
17:20:24 * danmcd is building smartos-live/illumos-joyent locally with this merged in before pushing it.
17:21:13 <danmcd> Meanwhile it's time for lunch and my favorite workflow:  "ssh $BUILDZONE pwait $PID_OF_BUILD ; say -a $EXTERNAL_SPEAKER Build is done, Dan"
17:22:02 <tsoome> :D
17:22:24 <tsoome> I have feeling, that mdb bit can be improved still;)
17:23:15 <tsoome> esp once 4.x will land
17:25:20 <otis> danmcd: "say" is a perfect tool, indeed.
18:01:53 <danmcd> tsoome: I expect you're right.  And looking forward to 41... I had a branch of it in illumos-joyent, not long after nfs-zone went back.  It likely needs to be massively rewhacked.
18:02:04 <danmcd> And yes @otis -> say(1) is one of MacOS's great features.
18:40:16 <yuripv> nice, didn't know about it
18:45:21 <tsoome> hrm. why.... ping: sendto Network is unreachable
18:49:21 <tsoome> reboot did fix it. weird.
20:36:00 <bahamat> Anybody know what ntpq means when it says a peer's refid is LOCAL(x)?
20:37:42 <sjorge> IIRC it's a local source only
20:37:47 <sjorge> so it could be the RTC
20:38:16 <bahamat> Even when the remote is an IP address?
20:38:39 <bahamat> And if a refid is LOCAL(x), does that mean there will be a subsequent line where the remote is LOCAL(x)?
20:41:02 <sjorge> it could be that the remote uses an undisiplined local source
20:41:34 <sjorge> e.g. i get it on my clients if both GPS sources and internet sources fail on my NTP server
20:42:06 <sjorge> it's only tracing locally as best it can from the last RTC read
20:42:14 <sjorge> aka very bad in my case
20:42:51 <sjorge> X is probably because it's not to be used unless no other source is available
20:43:11 <bahamat> Well the x is an integer
20:43:34 <bahamat> The line I'm parsing is this:
20:43:34 <bahamat> -216.218.254.202 LOCAL(1) 13151   5 u  646 1024  377   70.928   -4.351   1.224
20:43:46 <sjorge> https://www.meinbergglobal.com/english/info/ntp-refid.htm
20:43:58 <bahamat> That IP is clock.sjc.he.net, but when I use that as my time server, my refid isn't local.
20:44:38 <sjorge> the link also seems to indicate it's an undiciplined local source on the remote
20:45:25 <sjorge> ok the integer seems to be the X clock of that source type
20:47:31 <bahamat> I found this: https://serverfault.com/q/472455
20:47:36 <sjorge> https://gist.github.com/sjorge/f4b9f3e66a270198ab8557fd319aa5af e.g PPS(0) is my first local PPS source and GPS(0) my first GPS source, GPS(1) is my fallback GPS source, that one does not have a percise occilarion cristal
20:48:39 <bahamat> which doesn't exactly make things clear, but it makes me wonder if this user has a remote listed as LOCAL(x) to match that one with the refid of LOCAL(x)
20:49:05 <bahamat> Which, if they do and I don't fix it, I'm just moving the crash to the next line.
20:49:49 <bahamat> But I think in any case, it's possible for either remote or refid to be LOCAL(x), so I need my regexp to accommodate both.
20:50:52 <sjorge> the refid on a remote is what the it (remote) is using as it's primary source
20:51:32 <sjorge> with my above example from my server, my clients will show PPS(0) as the refid behind the remote ip
20:51:42 <bahamat> Ok, so then that should mean there won't necessarily be a line where the remote is LCOAL(x)
20:51:56 <sjorge> i think so yes
20:52:13 <sjorge> well i think you can have .LOCAL. LOCAL(0) ...
20:52:28 <bahamat> My regexp for that field is ([a-zA-Z0-9.]+)
20:52:45 <bahamat> which would be fine with the dots, but it's choking on the parens.
20:53:34 <bahamat> But I think to be on the safe side I should handle remote having parens in it as well.
20:54:15 <sjorge> see my gist from earlier
20:54:27 <sjorge> remote colum can certainly have () in it
20:56:33 <bahamat> Yeah.
20:56:38 <bahamat> OK, thanks, that's helpful.
21:00:51 <bahamat> sjorge: Can you tell me what's going on with line 7 in your gist?
21:59:27 <danmcd> @ptribble --> can't remember if you have push permission upon approval or not.
22:00:02 <danmcd> (Haven't RTI-reviewed your RTI, but knowing this a priori would be useful. )
22:00:40 <richlowe> you can look at people's roles in the bug tracker
22:01:04 <danmcd> OH!
22:03:27 <danmcd> Thank you Rich, sorry for the ping Peter.
22:03:42 <ptribble> I do (although being quiet haven't used it in a while)
22:08:32 <sjorge> bahamat: it's fqdn (ip) IIRC
22:08:50 <sjorge> but it usually gets truncated before it hits the ip
22:10:05 <sjorge> https://gist.github.com/sjorge/63aa5a8b73b8d9b1a4609c024a48784a
22:10:09 <bahamat> sjorge: Ok, so if you do -n for numeric only, then it shouldn't do that.
22:10:17 <sjorge> you might want to add -n i guess
22:10:24 <bahamat> Yeah, I do already
22:10:55 <sjorge> yeah, it also shows the PPS(0) and friends as the special ip ranges
22:11:15 <bahamat> I guess that should have been obvious earlier, but I was over thinking it.
22:11:59 <bahamat> Ok, so I may not actually have to handle it in the remote column.
22:12:17 <bahamat> But also, it doesn't seem like it would break anything if I do anyway.
22:12:28 <sjorge> so not ipv6 does very weer stuff too
22:12:37 <sjorge> *do note
22:13:25 <bahamat> Yeah, but I don't think we're doing anything with the remote and peer, we're just trying to get the delay/offset/jitter
22:16:12 <sjorge> i send you a privmsg with an ipv6 entry
22:16:40 <sjorge> as it's actually a global addr
22:16:57 <sjorge> i'm off to bed now though
22:16:59 <bahamat> Yeah...I should add :'s to my regexp so that those are supported