throwaway_se099

What is ample time for a company that hired a webdev one time to build them a static website and never checks webmaster@domain emails?

That kind of outfit is much more likely to be a victim of missed renewal or a myriad other technical screwups than a Google-initiated exit of the registrar business.

I feel like Google marketing has no idea the absolute monster of a problem they've created by allowing their business to get a reputation for being extremely unreliable in the B2B space.

They can certainly count on a spate of hyperventilating HN posts whenever they announce any kind of service-related news.

More seriously, their most celebrated servicides are consumer-oriented, like Google Reader. "Extremely unreliable in the B2B space" sounds like an exaggeration to me.

You need a permit (effectively, a visa) to enter the peninsula, and there is a daily quota. About a tenth of available permits can be issued to non-Orthodox visitors. They don't single out the Greek church from other Orthodox churches (AFAIK).

[I researched the entry requirements a couple of years ago out of curiosity, but never tried to actually visit. Something may have changed in the meantime, but somehow I doubt it :)]

UK MHRA: Dec 2. US FDA: Dec 11. European EMA/EC: Dec 21. Months later? Hyperbole doesn't help your argument.

It's rather unlikely that the first issue, which is an ordering problem during service shutdown, has much in common with timeouts during service startup, which you have described as your original issue.

The Stack Exchange question is a straightforward how-to for adjusting the timeouts.

5773 requests a clarification of the documentation of timeouts and signalling behavior.

3901 is a case of misplacing the timeout directive.

2047 is a sort of philosophical problem of reporting uniformity vs. consistency with manual configuration. The systemd team prefers the former, whereas I would prefer the latter for not violating the principle of least surprise, although I understand the reasons for choosing the first option.

Anyhow, I still don't see good support for your assertion of the complete lack of timeout documentation, just tangentially related distractions. A complex set of problems, and service management does qualify, will have edge cases, insufficiently clear documentation, and outright bugs, which is why software is never finished. Older init systems had all of these, but they didn't give you the tools to attempt to rectify the problems, so it was all more or less swept under the rug. Using a facile "shit, fullstop" characterization therefore tells me more about your views than the actual technical merits or documentation quality of systemd.

Nothing except three paragraphs in systemd.service(5) (TimeoutStartSec=, TimeoutStopSec=, TimeoutSec=), with references to systemd-system.conf(5) where the defaults are described. I wouldn't call that undocumented. Whether it should exist by default is another question; on balance, I'm glad it does.

To be clear, texting on a bicycle is not a good idea, helmet or no helmet.

That's internet in a nutshell, and HN is not that different despite pretensions to the contrary. What partly redeems it is the better than even chance that in posts with technical subjects, someone informed and/or competent will appear and write something worthy. You learn to filter out the rest.

That meeting was probably never on the official schedule. There are numerous ways to arrange such things off the books. The Gov's office can certainly provide the schedule which will give him plausible deniability, after which it's he said she said, unless another witness comes forward.

(If the above strikes you as too underhanded and sleazy, well, the whole affair is such. The lure of Amazon HQ2 was in play, remember.)

I think your timeline is a bit scrambled. Obama got the Nobel Peace (or rather, Not-GW-Bush-Jr) prize in the first year of his presidency, before any foreign interventions that could be realistically ascribed to his policy.

Vi has the insert-mode commands for indenting (Ctrl-T) and unindenting (Ctrl-D) the current line. If you're used to them, you don't really need Tab except for aligning things within the line. Also, Tab is Ctrl-I.

That's on the original Bourne shell and its author's evident love for Algol 68. Wikipedia has a fine summary.

Britannia Hospital?

Emulation is non-optional if one wants to avoid splitting the ecosystem.