brycec: whoa, glowing bear, hot damn..!
It's sweet
That's what she said!!
And since it's websockets, I could host it anywhere (or use their hosted copy) without worrying about some third-party connecting to my weechat (which is only listening on a VPN anyways)
nice
nice
ended up quitting today, haha
got contract networking work lined up starting next week so that worked out pretty well
m0unds: Congrats!!!
Hey nice work m0unds
ooh new Yosemite beta. Time to update.
Maybe I'm a bit jaded, cynical, and/or vindictive, but I'm deeply amused when a company keeps overloading a guy by letting his coworkers go and then he quits leaving the company fucked
"This is what happens..."
KARMA
And then they try to guilt you about it
heh, and I do feel bad for them, but that doesn't change my decision
I wouldn't.
This is what happens to people who do that.
meh, it's more a "I'm sorry, i wish it didn't have to be this way" kind of sympathy
yeah
the disappointmentt
Oh man Glowing Bear embeds media too. No need to click links, it's all inline (or a hidden by a button)
Reminds me of $name_of_osx_IRC_client
I don't think I'll ever get tired of people opening a ticket 2 weeks ago, getting a response within a couple hours, silence for 2 weeks and then they're calling in shouting "this is an emergency."
Not that I'll miss it, but I'm still entertained.
Hahahaha.
And in today's case, the dude's equipment is out of warranty by 2 years
Your failure to plan ahead does not make it my emergency.
Lol.
brycec: this was a 100% vindictive move on my part. ordinarily, i don't feel that way
but seeing the list of stuff that is pending and needing attention and knowing i won't have to deal with it is amazing
they're hiring back this idiot that i fired 2 years ago, purely because he went to this week long training seminar thing a couple years back for platform maintenance. he failed the exam and stuff, but i guess he's better than nothing. i don't think he knows the shitstorm he'll be walking into.
the company that does the solution engineering / sells the storage gear and software for surveillance offered me some contract work too, so i might take them up on that
Oh that's cool, nice of them
"Clearly you know our shit"
yeah
What does everyone recommend for backing up FreeBSD?
I'm using duplicity currently.
(same)
Also, zfs replication
zfs replication, eh
didn't know it had that.
That's what she said!!
Also, I don't run zfs.....
duplicity here too
looks like XO is having some problems...
doh
mtr -4 74.119.169.150
from the 174.136. etc.. block fails at denver
mtr from the 206.whatever block goes through
m0unds: zfs send | ssh zfs recv
i don't use zfs, just duplicity
I suppose not running zfs is a reasonable excuse for not being familiar with its capabilities
i've used it, just don't use it because my primary server-type-box is running netbsd
and they don't have working zfs yet
acf_: mine goes abq > sjc > nyc without any loss
that seems really round-about
haha
abq > sjc > nyc > denver > chicago > nashville..?
Spokane - Seattle - San Jose - New York, all on Comcast... then it hits XO and goes Denver, Chicago, Nashville.
bad rdns, bad
You wish
has to be
chi -> den isn't 1ms
sub 1ms, actually, like .6ms
haha
bah
chi-den wavers around 5ms for me
at least, the difference in ping times between those hops
but it varies +- 15ms
@geoip 207.88.12.57
207.88.12.57 is in United States
stupid duckduckgo...
haha
thanks for clarification
@weather autoip 207.88.12.21
Potwin, KS: Partly Cloudy ☁ 71°F (22°C), Humidity: 81%, Wind: From the ESE at 10.0 MPH Gusting to 10.0 MPH -- For more details including the forecast and almanac, see http://www.wunderground.com/cgi-bin/findweather/getForecast?query=37.960407,-97.173210 or re-request this with: @weather -v autoip 207.88.12.21
That's te-4-1-0.rar3.chicago-il.us.xo.net
(And wunderground's geoip db)
@weather autoip 207.88.12.57
Potwin, KS: Partly Cloudy ☁ 71°F (22°C), Humidity: 82%, Wind: From the ESE at 10.0 MPH Gusting to 10.0 MPH -- For more details including the forecast and almanac, see http://www.wunderground.com/cgi-bin/findweather/getForecast?query=37.960407,-97.173210 or re-request this with: @weather -v autoip 207.88.12.57
kansas is closer than chi for sure
that's the den hop
haha
@weather autoip 216.156.0.78
Potwin, KS: Partly Cloudy ☁ 71°F (22°C), Humidity: 81%, Wind: From the ESE at 10.0 MPH Gusting to 10.0 MPH -- For more details including the forecast and almanac, see http://www.wunderground.com/cgi-bin/findweather/getForecast?query=37.960407,-97.173210 or re-request this with: @weather -v autoip 216.156.0.78
nashville ^
I'm guessing the geoip is wrong and the rdns is right
woah
i'm
err
there is some really crazy crap going on
so if you input the chi ip in their lg, and use dfw as the originating network, it shows the rdns as denver
if you do it from chi it says it's chi
if you do it from dfw, it's 20ms and says den, but if you do it from chi it's 0ms and says it's chi
umm
that's not normal
goofy things are goofy
neither is this: http://paste.unixcube.org/k/ac3664
sweet
haha
so it works from 174.136.111.134
but not from 174.136.111.132
oh well
which upsets me, because that machine is *supposed* to be 174.136.111.132
so XO just decided to drop packets from that one specific address at denver?
lol, been leaving my mtr running... seen XO change from DEN-CHI-NAS to DAL-ATL-NASH
ah. how I'm going via atlanta
and all is well again... :)
yeah, same here
goofy xo
SORRY GUYZ WE BROKED IT
I love that my packets are going west -> east -> midwest -> east -> "the south"
Back and forth and back and forth
maybe something broke, so there is some funny routing?
or xo is always like this
mtr to xo.net - two hops outside comcast, with no routing
so, no idea
(And I don't plan to run mtr's to their lg servers)