--- Log opened Tue Jan 09 00:00:47 2018
00:29 -!- skiboy [skiboy@gateway/vpn/privateinternetaccess/skiboy] has quit [Ping timeout: 264 seconds]
00:36 -!- skiboy [skiboy@gateway/vpn/privateinternetaccess/skiboy] has joined #se2600
02:13 < aestetix> I just coined a new term
02:13 < aestetix> ebonics is when ghetto speak is so far removed from english it becomes its own language
02:14 < aestetix> so when you have a bunch of silicon valley rich idiots who make nonsense phrases and redefine words into ways that make no sense
02:14 < aestetix> we can call it "bayonics"
06:28 -!- Dolemite [~scott@96-38-109-185.dhcp.jcsn.tn.charter.com] has joined #se2600
06:28 -!- mode/#se2600 [+o Dolemite] by ChanServ
06:28 <@Dolemite> mr0ning, be0tches and h0ez!
06:29 <@Dolemite> Inbox == 1198 unread messages.    I know what I'm doing for the next few hours.   Hitting the delete button, over and over.  LOL
06:44  * aestetix hugs Dolemite 
06:53 <@Dolemite> So what'd I miss?
06:53 <@Dolemite> Something about 486/DX chips being popular, again?
07:05 < aestetix> Oprah 2020
07:14 <@Dolemite> Oh fuck that noise
07:14 <@Dolemite> Send me back to the Caribbean
07:22 < aestetix> So
07:22 < aestetix> Is there any actual way to fix this meltdown/spectre thing?
07:23 < aestetix> They have a website with pretty logos and whitepapers, and no fix
07:23 <@Evilpig> aestetix: use amd, but not with windows since it appears the windows patch for it is bricking systems
07:23 < aestetix> so no
07:25 < aestetix> https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown
07:25 < PigBot> Title: SecurityTeam/KnowledgeBase/SpectreAndMeltdown - Ubuntu Wiki (at wiki.ubuntu.com) http://tinyurl.com/y97p473g
07:25 < aestetix> "Candidate kernels are beginning to be made available for testing"
07:25 < aestetix> that doesn't sound very confident to me
07:45 < aestetix> so
07:45 < aestetix> why was meltdown/etc revealed early?
07:48 <@Corydon76> Given that the CERT IDs for the issues were issued back in 2017, I suspect it was starting to leak, so the authors came forward, instead of perhaps letting the Dark Web engineer an exploit first.
07:49 <@Corydon76> lkml certainly knew long before then
07:49 < aestetix> makes sense
07:49 < aestetix> sort of
07:49 < aestetix> "back in 2017" given that it's only jan 9th....
07:50 <@Corydon76> The initial disclosure to the chip makers happened in July.
07:51 < aestetix> so you mean back in mid-2017
07:51 <@Corydon76> I don't know when it was disclosed to the kernel team or Microsoft, but it was probably shortly thereafter.
07:53 < aestetix> and they are still working on a fix
07:53 < aestetix> it must be a doosey
07:55 <@Corydon76> There's a balance to be had.  Yes, they can fix it right now, but at an incredible loss of CPU efficiency.
07:55 <@Corydon76> If you were told that a particular patch will fix the vulnerability, but you'd lose 30% efficiency, you might delay until there was a concrete threat.
08:28 -!- FluxS0Ul [~FluxS0Ul@64.31.254.218] has joined #se2600
08:35 -!- remoford [~remo_lapt@c-69-137-84-154.hsd1.tn.comcast.net] has joined #se2600
08:42 -!- FluxS0Ul [~FluxS0Ul@64.31.254.218] has quit [Ping timeout: 268 seconds]
08:42 -!- FluxS0Ul [~FluxS0Ul@64.31.254.218] has joined #se2600
09:32 <@Dolemite> Man, I was gone for nearly 2 weeks.   I expected my LTC to have quadrupled in that time.   Don't these people know how a bubble is supposed to work?
09:39 < xray> Google says they may have a novel fix for Metdown/Spectre https://security.googleblog.com/2018/01/more-details-about-mitigations-for-cpu_4.html
09:39 < PigBot> Title: Google Online Security Blog: More details about mitigations for the CPU Speculative Execution issue (at security.googleblog.com) http://tinyurl.com/yaueopkc
09:51 -!- skiboy [skiboy@gateway/vpn/privateinternetaccess/skiboy] has quit [Quit: Leaving]
10:02 < aestetix> Dolemite: I have bad news for you
10:02 < aestetix> https://electionbettingodds.com/
10:02 < PigBot> Title: Election Betting Odds by Maxim Lott and John Stossel (at electionbettingodds.com) http://tinyurl.com/pnqgezv
10:03 < aestetix> look who is at number 2
10:04 < xray> Have you seen the movie Idiocracy?
10:14 <@Evilpig> I think I can safely say that there isn't a single person in this channel that hasn't.  it's probably just as safe a bet that everyone in here can make at least one quote from it
10:22 < xray> It was a rhetorical question in response to the election odds post.
10:23 <@Evilpig> non-rhetorical question.  how the fuck can this exit out with a -1 return code?  https://gist.github.com/wilpig/d4e58c00d41e8488d3d151059c0e27f8
10:23 < PigBot> Title: reboot counter · GitHub (at gist.github.com) http://tinyurl.com/yal922fc
10:24 <@Evilpig> in my log I see "60 sec"  then it exits -1
10:25 <@Corydon76> Evilpig: I wasn't aware that you can do a self-decrement like that in bash
10:25 <@Corydon76> Generally you have to use the form x=((x-1))
10:26 <@Evilpig> I can try changing it but it works when I run it by hand
10:27 <@Corydon76> Also, I would put a she-bang at the top, so it definitely runs in bash, not sh.
10:27 <@Evilpig> this is just a tiny part of a larger script
10:27 <@Evilpig> it's got the shebang
10:28 <@Evilpig> I'm looking at the log and it might be that because the error is coming one second after the 60 sec is echoed
10:28 <@Evilpig> the other oddity is it doesn't happen every time either
10:31 < aestetix> https://www.itwire.com/security/81338-handling-of-cpu-bug-disclosure-incredibly-bad-openbsd-s-de-raadt.html
10:31 < PigBot> Title: iTWire - Handling of CPU bugs disclosure 'incredibly bad': OpenBSD's de Raadt (at www.itwire.com) http://tinyurl.com/y7fzyj47
11:16 -!- sasquatc4 [~sasquatch@c-71-56-244-10.hsd1.co.comcast.net] has joined #se2600
11:16 -!- mode/#se2600 [+o sasquatc4] by ChanServ
11:18 -!- ezelkow1 [~sasquatch@2601:282:702:1eb8:e8be:e05f:35bb:96a0] has quit [Ping timeout: 252 seconds]
11:45 -!- sasquatc4 is now known as ezelkow1
11:47 <@Catonic> OW MY BALLS!
11:50 <@ezelkow1> go away! batin!
11:50 < xray> Catonic: LoL
11:50 < xray> I got the reference
12:03 <@Evilpig> Corydon76: found the cause of the error.  so earlier just before the echos start there was a REBOOT=`/sbin/shutdown -r +1 &`
12:03 <@Corydon76> So it exited because the process was sent a TERM signal?
12:03 <@Evilpig> Ideally this would be scheduling a reboot to happen 60 seconds in the future.  on rhel7 it does.  on rhel6 the script is waiting until that command finishes and then the countdown starts
12:04 <@Evilpig> so yes, the script terminated with the -1 because the reboot was triggered.
12:04 <@Corydon76> Ah, yeah, that'll do it
12:05 <@Evilpig> I am guessing that on rhel7 shutdown is passing that command off to system-duh and it responds back to the script htat the command finished and in the case of rhel6 it's dealing with init and just waiting to process
12:06 <@Corydon76> Strange that it wouldn't let you fork a process into the background
12:07 <@Evilpig> I wanna say that we've tried forking it before with other methods too that didn't work, it just always held onto it.  and it might not be bash entirely to blame but something with rundeck that we're using to run these jobs remotely
12:09 <@Corydon76> On some systems, when you fork, you also have to set a new session ID, or the parent will wait until the child exits
12:09 <@Corydon76> Normally that's only a concern when you're forking in C
12:11 <@Evilpig> we've tried stuff with nohup and setsid
12:11 <@Corydon76> setsid should help with that problem.  Nohup only stops the signal.
12:20 <@_NSAKEY> Evilpig: Just yank the power cord. Nothing bad has ever come from that.
12:22 -!- K4k [elw@unaffiliated/k4k] has joined #se2600
12:28 <@Evilpig> Corydon76: not sure how this is holding the job but I don't think I can abstract it any more at this point.  I made a quick helper called /whatever/reboot  and put 
12:28 <@Evilpig> #!/bin/bash
12:28 <@Evilpig>  /sbin/shutdown -r +1 &
12:29 <@Evilpig> in it. the in my primary script I called it like setsid /whatever/reboot
12:29 <@Evilpig> so it should be completely detached from my main process but it's still holding up
12:30 <@Corydon76> That sounds like a bash bug
12:31 <@Evilpig> not sure what it is,  really annoying
12:35 <@Evilpig> https://unix.stackexchange.com/questions/165991/shutdown-program-doesnt-terminate-after-scheduling-a-shutdown
12:35 < PigBot> Title: command line - shutdown program doesnt terminate after scheduling a shutdown - Unix & Linux Stack Exchange (at unix.stackexchange.com) http://tinyurl.com/y9cagb2b
12:35 <@Evilpig> seems this is just an issue with shutdown specifically
12:36 <@Corydon76> You can fork another long-running process?
12:37 <@Corydon76> Another option might be to call it twice, once with the -k option, and the second with the +0 time option.
12:38 <@Corydon76> That way, you won't actually have the process in the background to deal with
12:39 <@Evilpig> I think that will still lead to the error we were having where rundeck was being retarded and holding onto the process.  but let me give that a go
12:39 <@Evilpig> I'll throw the k before the loop and the -r +0 after the loop completes
12:39 <@Catonic> If all else fails, yank the power out from under the server like a chair
12:39 <@Evilpig> Catonic: if I could automate the power cord getting yanked I would
12:40 <@Corydon76> Evilpig: Also, on the final invocation of shutdown, use the exec prefix, so it replaces the script, and the script won't get terminated in the logs
12:41 <@Catonic> halt --skewer-kernel now
12:46 <@Evilpig> Corydon76: not sure if it was the exec or the +0 but I got a complete that time
12:47 <@Evilpig> either way I have a fix.  thank you for the suggestions
12:47 <@Corydon76> Excellent
12:47 <@Evilpig> REBOOT=`/sbin/shutdown -k &`
12:48 <@Evilpig> this here threw and error about expecting time so i'm just going to omit it
12:48 <@Evilpig> shouldn't really be an issue if someone logs in at that point anyhow
12:48 <@Corydon76> You want -kr +1 on that
12:48 <@Corydon76> You want it to "wall" a message that the system is rebooting in a minute's time
12:49 <@Evilpig> I could just throw up a wall message instead
12:49 <@Corydon76> And I don't think you need to background it
12:51 <@Corydon76> Unfortunately, the manpage is not clean on that.
12:51 <@Catonic> wall "Normal shutdown in ten minutes; axe through the CPU in five."
13:02 <@_NSAKEY> Evilpig: At work, we have the servers set up to auto-boot when power is applied. Sometimes, we yank power out from under them via the PDU.
13:02 <@_NSAKEY> Not quite automated, but better than sending someone out to physically deal with cabling.
13:02 <@Evilpig> it's all good.  we just ran it against rhel5,6,7 and all showed the auto update job complete in rundeck
13:17 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has quit [Quit: ZNC 1.7.x-git-847-5132ea98 - https://znc.in]
13:37 < aestetix> so
13:37 < aestetix> are fidget spinners still a thing?
13:38 <@opticron> there are even spinners that have BT that will tell an app on your phone how fast they're spinning
13:38 < aestetix> ....
13:39 <@opticron> and have a speaker built into them
13:42 <@_NSAKEY> aestetix: They stopped selling them in the clearance aisle at my local walmart recently, so I would say no.
13:42 <@_NSAKEY> They were going for $1 apiece.
13:47 <@rattle> Slack is down.  IRC is cool again!  WOOHOO!
13:48 <@Evilpig> slack is down, yes.  damnit.
13:48 <@Evilpig> just had two different people pop their heads in here asking that
13:48 <@Evilpig> crazy how much we depend on that to communicate
13:50 < aestetix> https://status.slack.com/
13:50 < PigBot> Title: Slack System Status (at status.slack.com) http://tinyurl.com/otaqv5h
13:50 <@Dagmar> * BEGIN RUNNING IN CIRCLES
13:50 <@Evilpig> while slack is down i'm trying to get netdata to stream data to multiple hosts
13:51 <@Evilpig> https://github.com/firehol/netdata/wiki/Replication-Overview
13:51 < PigBot> Title: Replication Overview · firehol/netdata Wiki · GitHub (at github.com) http://tinyurl.com/kdz7w9c
14:40 -!- skiboy [skiboy@gateway/vpn/privateinternetaccess/skiboy] has joined #se2600
14:48 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has joined #se2600
14:50 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has quit [Client Quit]
14:59 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has joined #se2600
15:00 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has quit [Remote host closed the connection]
15:02 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has joined #se2600
15:02 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has quit [Remote host closed the connection]
15:06 -!- cyberanger [~cyberange@swissknife/adak/infocop411] has joined #se2600
15:08 <@Catonic> lmao, slack is down
15:08 <@Catonic> break out discord
15:15 <@Evilpig> but I don't have a discord bot tied into all of our various systems
15:20 <@ezelkow1> discord bots are fairly easy to write: https://github.com/ezelkow1/discord-key-bot :)
15:20 < PigBot> Title: GitHub - ezelkow1/discord-key-bot: A bot for discord that accepts, announces, and gives out keys (at github.com) http://tinyurl.com/y8evs8b3
15:20 <@ezelkow1> that took like 6-8hrs of total work
15:21 <@ezelkow1> course i dunno what it looks like as far as non-go api's, thats the only one ive looked at
15:21 <@Evilpig> I'd hate to see how many hours I have in our slack bot
16:10 < xray> https://arstechnica.com/tech-policy/2018/01/att-and-comcast-finalize-court-victory-over-nashville-and-google-fiber/
16:10 < PigBot> Title: AT and Comcast finalize court victory over Nashville and Google Fiber | Ars Technica (at arstechnica.com) http://tinyurl.com/y7g4kypu
16:53 -!- FluxS0Ul [~FluxS0Ul@64.31.254.218] has quit []
17:27 <@Evilpig> it's a sad day in nashville for that 
17:27 <@Evilpig> I read that earlier and was irritated at NES's lack of interest
18:33 -!- sasquatc4 [~sasquatch@c-71-56-244-10.hsd1.co.comcast.net] has joined #se2600
18:33 -!- mode/#se2600 [+o sasquatc4] by ChanServ
18:36 -!- ezelkow1 [~sasquatch@c-71-56-244-10.hsd1.co.comcast.net] has quit [Ping timeout: 248 seconds]
19:18 -!- sasquatc4 is now known as ezelkow1
19:27 -!- crashcartpro [uid29931@gateway/web/irccloud.com/x-nxhmbbkcnvksgauy] has quit [Quit: Connection closed for inactivity]
22:47 -!- LastChild [~RasPi@71.228.205.189] has quit [Ping timeout: 272 seconds]
23:02 -!- LastChild [~RasPi@71.228.205.189] has joined #se2600
23:02 -!- mode/#se2600 [+o LastChild] by ChanServ
23:18 -!- klixa-cloud [uid861@gateway/web/irccloud.com/x-ngqeswinvsqbnrzm] has joined #se2600
23:18 -!- mode/#se2600 [+o klixa-cloud] by ChanServ
--- Log closed Wed Jan 10 00:00:49 2018