155 karma · joined August 29, 2016
When I place the wrong finger on my touchID and press the home button once, it shows me the pin entry to get into the phone. No multiple presses, nothing. First bad read, shows the pin entry.
The only thing that Apple could have done is bump the CPU, which would have not gained anything in terms of power savings or any other changes, and means now you have one more model you have to stock replacement parts for.
This has been an issue not just for laptops, but also for their Xeon line-up in servers. Due to manufacturing delays the v4 for the Xeon line-up was released earlier this year, and didn't really get started shipping until April.
A lot of apps let you select the season from some sort of "drop down" or display a list of seasons vertically and let you scroll through individual episodes horizontally within that season...
Revocation cost $59 at the time. Was painful.
Ouch that sucks.
but if it works.
sqlite3 ~/Library/Keychains/*/ocspcache.sqlite3 'DELETE FROM ocsp WHERE hex(serialNum) IN ("040000000001444EF03E20", "040000000001444EF04247");'
What a pain in the behind :/My CentOS 7 OSD nodes will sometimes not complete booting because it's hung somewhere in the boot process. There is no way to tell systemd to continue, Ctrl + C doesn't do anything and there is no way to get into the system because sshd is still not running.
Booting it in debug mode to try and get more information makes the whole thing work.
Also, when a unit file gets stuck, it goes into this waiting loop, which is a giant pain in the behind... I want to try and fix it, not wait 10+ minutes for the unit files to time out.
Ctrl + C should immediately stop what it is trying to do and dump me into some sort of login shell so that I can then go and fix the issue...
I've also had issues on Ubuntu 16.04 because of third party software that doesn't correctly set up it's Requires/Wants/Before/After's and then systemd will happily hang the whole boot process. Worst thing is that these issues become more and more apparent on systems with more cores/CPU's... so the 44 core, 88 thread systems we have show the issue way more than the 4 thread desktop that developers are using...
Instead they want me to sign into Google and it wants that info to then be stored on Google's servers.
Open some app: Would you like me to be the default for X? Me: no thanks.
Next day:
open some app: Would you like me to be the default for X? Me: ahhh, NOT AGAIN.
Or have we forgotten how annoying it is that browsers all seem to do that all the damn time.
This allows me to have one central server that is well secured and protected that allows ingress from the remote hosts, and then all the clients reach out to the master to get their tasks.
while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""; done
Try this. As soon as you loop it, the bug is hit pretty quickly.It's a valid TLD...
https://www.icann.org/news/announcement-2-2014-08-01-en
shows why drive. was set to return 127.0.53.53.
Same thing happened with prod. and other TLD's. These are all names that were/are being used internally and now are valid TLD's that are going to cause issues for people :/
There is none of this 127/8 mess.