Pretty sure speeding in that range would net a fixed penalty of 3 points. Also, she would have had the first 3 points discounted via an awareness course. So, in effect this is likely the 5th offense, or less if one or more of the others was serious enough to get 6 points.
r00ty
joined 2 years ago
I initially thought that. But the article makes it clear. But you need to know how our licenses work.
Normally for speeding (up to 42mph in a 30) you would get as a first offense the choice of paying for a speed awareness course OR 3 points + fine, and 43-49mph you would get a fixed penalty of 3 points and a fine. Subsequent offenses would go straight to points + fine.
However the points are important. Your points expire after 3 years. But if you have 12 active points at any time, you will then get a compulsory ban (unless you can prove to a court you need to drive, which is abused of course). Which is what likely happened here.
So, she's been quite the habitual offender.
I was looking at doing something similar with my Asustor NAS. That is, supply the voltage, battery, charging circuit myself, and add one of those CH347 USB boards to provide I2C/GPIO etc and just have the charging circuit also provide a voltage good signal that software on the NAS could poll and use to shut down.
My understanding is that the only issues were the write hole on power loss for raid 5/6 and rebuild failures due to un-seen damage to surviving drives.
Issues with single drive rebuild failures should be largely mitigated by regular drive surface checks and scrubbing if the filesystem supports it. This should ensure that any single drive errors that might have been masked by raid are removed and all drives contain the correct data.
The write hole itself could be entirely mitigated since the OP is building their own system. What I mean by that is that they could include a "mini UPS" to keep 12v/5v up long enough to shut down gracefully in a power loss scenario (use a GPIO for "power good" signal). Now, back in the day we had raid controllers with battery backup to hold the cache memory contents and flush it to disk on regaining power. But, those became super rare quite some time ago now. Also, hardware raid was always a problem with getting a compatible replacement if the actual controller died.
Is there another issue with raid 5/6 that I'm not aware of?
Trinitycore has a guide https://trinitycore.info/ if you follow it properly it will result in a working server. Any time I've seen someone have a problem following it, they either missed a step by mistake, or tried to go off on a tangent, configuring it for their own needs during install/setup.
First make it work with the instructions, and once it is working, then tinker with it :P
It's more likely trinitycore (which forked from mangos quite some time ago). https://github.com/TrinityCore/TrinityCore/
Mangos do still have a Wrath server branch. But specifically for 3.3.5 trinitycore is more often used.
It's an old expression, but it checks out.
Source: Somewhat old(ish) person from the UK.
This was actually the story I had in mind when I wrote my comment. In my case, I'm using cloudflare for this mbin instance, another unrelated low traffic site, and R2 for the media on the instance. It's so small that it will never really escape their free tier.
But yeah, if you're doing something that is scaling up this is definitely something you need to be aware of.
There seems to be a line, so far as I can tell. If everything you need sits on the free tier, they're really good (well tbh their R2 storage is reasonably priced too). But once you stray into needing a paid tier, it apparently (I'm not there) quickly gets expensive as you're lured into every higher tiers.
But yes, in general I don't mind cloudflare so much and do use their free (and R2 paid) services.
Am I the only person that would be surprised if this place wasn't inhumane at this point?
No, he used a Delorean because of the style, and something about the stainless steel construction that we'll never know the rest of. :P
I think so. I would consider perhaps allowing a short time without power before doing that. To handle short cuts and brownouts.
So perhaps poll once per minute, if no power for more than 5 polls trigger a shutdown. Make sure you can provide power for at least twice as long as the grace period. You could be a bit more flash and measure the battery voltage and if it drops below a certain threshold send a more urgent shutdown on another gpio. But really if the batteries are good for 20mins+ then it should be quite safe to do it on a timer.
The logic could be a bit more nuanced, to handle multiple short power cuts in succession to shorten the grace period (since the batteries could be drained somewhat). But this is all icing on the cake I would say.