lykron

You could do this with the `timeout` command.

`timeout -s SIGINT 1h restic...`

That would let restic run for one hour, and then once the hour elapses send a SIGINT which will stop the process (see https://github.com/restic/restic/blob/a29777f46794ea4e35548f...)

They are. Small Business Cards are always are. It's not tied to my credit report, but my report was pulled as part of the process.

American Express gives out credit cards like candy. We make 600/month and Amex have us 40k in credit. It’s aslo cheaper than their offering.

It looks like an interesting product, but I’m surprised that Chase or Amex hasn’t attacked the market segment.

He didn't talk much about this, but I find it very hard to believe that they were able to make their own deposit application and get it certified for use (unless the UK has vastly different banking regulations than the US). 32-bit/64-bit systems have small rounding errors that are show-stoppers for banking from what I've heard. There is a reason why COBOL and Big Iron rain supreme in Finance.

Linode offers a shared private network per datacenter.

Yeah. Nobody is perfect, but Linode's technical features and support makes up for it in my book.

Feel free to show some love: https://www.linode.com/?r=a1baa5d9cdf4db262bb748108359572ffe...

Linode, except for DDoSs, has been incredibly solid.

"skills and efforts required to fulfill the ops responsibilities do not justify the need for such specialization." You just pay someone else to do it; get over yourself.

They've always had the functionality to run software like Transmission inside a Jail. I guess they just moved that functionality to docker to be more "hip".

I'm not saying to use AD for a SaaS product, I'm saying the advice on having an obscure domain is a bad one. The SaaS product is saas.com, the company domain is company.com, and the IPA or AD Domain is domain.company.com. I don't see any good reason to have a 3rd domain floating around for directory services. If anything it is another thing to manage and keep track of.

ElasticByte looks kinda cool. I'm curious to the market for it, as you seem to fit between "We can use heroku" and "We can hire two people."

"A third domain is needed for internal use and back office. This domain would probably be registered anonymously, so it would be a little more difficult to find."

Um, security through obscurity is not security. And I don't get this? Are we talking Active Directory? It can be a subdomain off your root domain that is only accessible internally.

Nothing you describe hasn't already been done by others.

The Silicon Valley double standard, but I would like a bit more concrete evidence before I get my pitchfork out.

DigitalOcean seems to be going after Linode. Will be interesting to see how Linode responds.

While I like this idea, the burden is shifted to the students couldn't get a scholarship; Students who are probably working to pay for school or have taken out loans that will take years to pay for.

A good article pointing out that it is not enough to complain or be a keyboard warrior, but you have to take tangible action in order to get effective results. A bit firm, but needed as this is the first time I've seen this issue with FetLife raised outside of FetLife.

Cheaper to buy standardized cells at scale, due to production capacity?

You forgot an /s when you said the pay gap. If you didn't, then they pay gap you refer to is a statistical figure that is observed when you compare every worker across every profession across their entire career. The pay gap (as you assert it) doesn't exist (nor is legal to have) at a company level.

If anyone is looking to jump ship, DreamWidth is a fork of LiveJournal.

That's my assumption as well. They have done massive amounts of custom work in CryEngine, so I'm guessing they are just using some features of Lumberyard.

Don't get me wrong, I've encountered issues before but CentOS 7.2 and Fedora 24/25 have been good to me.

Everytime I read posts like this, I think I must be the lucky one. Fedora 25 on my laptop and desktop, and I've had no issues what so ever.

The author's package manager complaints are unfounded. Complaining about yum, and yum being replaced by dnf? C'Mon, software evolves and sometimes you have to do a hard fork.

The complaints about NFS seem to be a backend issue, and not an issue with the client.

They don't need another datacenter. AWS has had more issues they NYI's datacenters have had in the past year. There are many companies that are based out of a single datacenter that haven't had any major issues.

Docker, and Kubernetes is still a rapidly evolving technology and there are too many horror stories of it crashing and burning in production for it to be worth it, in my view. Databases are not immutable, and even though Docker has persistent volumes it is still new and evolving. If the database breaks in some way, I don't want to have to worry about the new container having a slightly different patch level and that messing up the database. I don't want to have to worry about rebuilding my database cluster to upgrade it.

Google might do some really cool shit with Kubernetes, but they are Google. I don't think using them as a good example for anything but infrastructure on a massive scale is correct. They are years ahead of everyone else, and if they are doing something in production, they have been testing it for years. If shit hits the fan, they have thousands of employees to throw at the problem. GitLab is building a team, and therefore does not have the experience to know these systems inside and out. In my view, using Docker/Kubernetes is adding unnecessary complexity to the database fabric for minimal tradeoffs.

And considering that they are speaking out dedicated database servers, it makes no sense to add a unneeded layer of abstraction when in all likelihood the container will be bound to a node.

I'm not saying that you wouldn't see any performance gain. 2TB on the outer track will be faster than 8TBs on the same 8TB disk, but I'm saying any gains will be lost due the dense nature of the drives.

A quick google search shows that there are marginal gains on the outer track vs the inner, but that is only on sequential workloads. For something like GitLab, the workloads would be anything but.

http://superuser.com/questions/643013/are-partitions-to-the-...

https://www.pythian.com/blog/hard-drive-inner-or-outer/

I hope to god you are not using Kubernetes for your databases.

That would be something I would test. I don't know Ceph, so I would be taking a shot in the dark. I would guess it would not make much of a difference as everything is block level. I, personally, would do 1x PCIe SSD for cache, 1x 2/4TB SSD, and 2x 4TB HDD for each storage node.

Edit. If Ceph is smart enough, it would be aware of the tiers present on the node, and would tier blocks on that node. So a Block on node A will stay on node A.

I'm not super well-versed in the networking area. I misread the posting. I thought they were looking at 64Us of servers.

I've just gotten the notion that SDN is almost ready for primetime, just not yet.