dc2447

> Is privilege escalation that easy/common? Thinking esp of the number of shared hosting providers out there, if a user account is compromised they don't assume the entire server is compromised.

Privilege escalation is easier than getting the initial shell. I would certainly reinstall any machine where someone has a shell.

As for these web shells, this agin demonstrates the important of blocking outbound connections with a firewall or some type of networking design.

I have been approached a few times to interview for "Director, Site Reliability Engineering", which as far as I could tell was leading up the SRE team in Europe.

I had a few conversations but did not take it further. My reasoning was not going further was not the nature of the interview process, although I found it a little strange that they expected a director level position to know how many bits were in a mac address or nature of google as a business but the description of what the engineering team did for the majority of the time. Rather than building 'stuff' the team seemed to be involved in very low level debugging on the Google infra and apps.

I know somebody has to do that stuff but it's not something I was very sold on when it was described to me.

Incidentally the role is still being advertised so maybe finding engineering directors that know how many bits in a mac address or what the default signal sent with a kill command :)

http://www.linkedin.com/jobs2/view/10632280

There is another path, in the UK at least, which is to join the public sector, become employed by the state.

I like them all. A few years ago I would get irked by some things redhat did v debian derivatives and vice versa but now not so much.

I am just super glad after all these years we are all able to download and use (for free mostly) such an excellent OS.

> Elasticsearch mostly "just works", and we didn't have to worry about complex schema definitions, working with giant complex XML files (hello Solr)

If you were using Solr there are a few operational modes to run in. Config file based or SolrCloud[0]. The latter is more akin the ES in terms of cluster management.

I agree though from an simplicity of deployment perspective at scale ES is has a much lighter learning curve.

[0] https://cwiki.apache.org/confluence/display/solr/SolrCloud

> In what situations would a delayed replica be useful?

When we start to have slightly larger databases (multi terabyte) then delayed replicas become a very useful backup and recovery strategy. Typically we need to recover databases when there has either been human error (someone deletes a bunch of data they should not have) or a compromise. In these situations rather than restoring for a nightly backup it is _always_ faster to roll a delayed replica forward and promote it to be master then resync all the normal replicas.

> Time delayed replication standbys

Indeed, huge. Mysql has a relatively mature lag replica history now albeit via Percona. Adding delayed replicas to Postgres will be fantastic.

So much potential for IAP

I want to love Android. I really, genuinely do.

I have tried and tried many times but three of my four issues are unresolved.

1. Lagging (fixed I think) 2. No good email client that supports Exchange[1] 3. Plasticky build quality [2] 4. Very, very weak keyboard input

[1] Plus having to encrypt SD card makes Android slower [2] Yes, HTC One is better

I you want to monitor elastic search with Graphite then Collectd provides an excellent curl-json plugin which works really well with the ES health api

https://gist.github.com/dc2447/6783658

URLS were and I assume still are a massive part of the collective thought process in the Guardian but yeah, if you are GU then the internet will take whatever you say as canonical to be canonical regardless of seo strategy

We[0] have the GU domain because the Guardian was previously Guardian Unlimited.

[0] No longer there but still think of GU very fondly

This article is showing it's age. How likely is it like we are going to cache the 'welcome page' for Bob or Alice in 2013? It's pretty unlikely unless there is either zero personalisation on the welcome page or there is some Javascript hacked in to personalise the page.

More interesting is caching between our front ends and the back ends. Your backends are all serving up content over http these days so caching here makes much more sense.

Exactly the point I was thinking

Personally jgrep seems a better choice here

curl foo/bar.json | jgrep -n -s 'property'

Or even better

curl foo/bar.json | jgrep 'status=500' -n -s 'path'

http://jgrep.org/

The difference between iMessage and BBM is reliability. Anyone who has used iMessage on multiple devices will no doubt attest to the delivery issues.

I'm fairly ok with Keynote presentations taking time to sync down or issues with photostream syncing but when a message from my wife asking me to pick up the kids from school comes in three hours later then I have a massive issue with the product.

Why does apple find it so hard to get online services right?

Ironically in my experience BBM 'just works' the way Apple products used to.

By the way I would not be surprised to see Apple blocking BBM as it duplicates existing functionality on IOS

jgrep?

There is a massive demand for talent in all the cities mentioned in the thread. Places like Amsterdam and Berlin have a pretty signifant skills gap. I tend to see people who would perhaps struggle to get gigs in London get relatively senior positions elsewhere.

As for London being expensive to live, that really depends on where you live, there are some very affordable areas if you are willing to commute and the other costs of living (bar travel) seem comprable in my experience.

Good luck

What is the index URL format