That was my basic assessment as well, I’m not sure the gains are worth trying to unlearn 30+ years of ingrained keyboard habits! Thanks for your take on the subject
That was my basic assessment as well, I’m not sure the gains are worth trying to unlearn 30+ years of ingrained keyboard habits! Thanks for your take on the subject
That’s a possible answer, frequently cited by advocates of endless population growth. History is certainly rife with prioritization of economy over people, so it’s an easy place to land.
Accidental? Do better, Russia. America hits its targets.
Random question for a keyboard aficionado: have you investigated the CharaChorder?
kill -9
Just tested, thanks for the suggestion! It killed a few instances of rsync
, but there are two apparently stuck open. I issued reboot
and the system seemed to hang while waiting for rsync
to be killed and failed to unmount the zpool.
Syslog errors:
Dec 31 16:53:34 halnas kernel: [54537.789982] #PF: error_code(0x0002) - not-present page
Jan 1 12:57:19 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) being skipped.
Jan 1 12:57:19 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (timer based) being skipped.
Jan 1 12:57:19 halnas kernel: [ 1.119609] pcieport 0000:00:1b.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 12:57:19 halnas kernel: [ 1.120020] pcieport 0000:00:1d.2: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 12:57:19 halnas kernel: [ 1.120315] pcieport 0000:00:1d.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas kernel: [ 1.119415] pcieport 0000:00:1b.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas kernel: [ 1.119814] pcieport 0000:00:1d.2: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas kernel: [ 1.120112] pcieport 0000:00:1d.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) being skipped.
Jan 1 22:59:08 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (timer based) being skipped.
Jan 2 02:23:18 halnas kernel: [12293.792282] gdbus[2809399]: segfault at 7ff71a8272e8 ip 00007ff7186f8045 sp 00007fffd5088de0 error 4 in libgio-2.0.so.0.7200.4[7ff718688000+111000]
Jan 2 02:23:22 halnas kernel: [12297.315463] unattended-upgr[2810494]: segfault at 7f4c1e8552e8 ip 00007f4c1c726045 sp 00007ffd1b866230 error 4 in libgio-2.0.so.0.7200.4[7f4c1c6b6000+111000]
Jan 2 03:46:29 halnas kernel: [17284.221594] #PF: error_code(0x0002) - not-present page
Jan 2 06:09:50 halnas kernel: [25885.115060] unattended-upgr[4109474]: segfault at 7faa356252e8 ip 00007faa334f6045 sp 00007ffefed011a0 error 4 in libgio-2.0.so.0.7200.4[7faa33486000+111000]
Jan 2 07:07:53 halnas kernel: [29368.241593] unattended-upgr[4109637]: segfault at 7f73f756c2e8 ip 00007f73f543d045 sp 00007ffc61f04ea0 error 4 in libgio-2.0.so.0.7200.4[7f73f53cd000+111000]
Jan 2 09:12:52 halnas kernel: [36867.632220] pool-fwupdmgr[4109819]: segfault at 7fcf244832e8 ip 00007fcf22354045 sp 00007fcf1dc00770 error 4 in libgio-2.0.so.0.7200.4[7fcf222e4000+111000]
Jan 2 12:37:50 halnas kernel: [49165.218100] #PF: error_code(0x0002) - not-present page
Jan 2 19:57:53 halnas kernel: [75568.443218] unattended-upgr[4110958]: segfault at 7fc4cab112e8 ip 00007fc4c89e2045 sp 00007fffb4ae2d90 error 4 in libgio-2.0.so.0.7200.4[7fc4c8972000+111000]
Jan 3 00:54:51 halnas snapd[1367]: stateengine.go:149: state ensure error: Post "https://api.snapcraft.io/v2/snaps/refresh": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I believe there’s another issue. ZFS has been using nearly all RAM (which is fine, I only need RAM for system and ZFS anyway, there’s nothing else running on this box), but I was pretty convinced while I was looking that I don’t have dedup turned on. Thanks for your suggestions and links!
I did, great suggestion. It never recovered.
Thank you! I ended up connecting them directly to the main board and had the same result with rsync, eventually the zpool becomes inaccessible until reboot (ofc there may be other ways to recover it without reboot).
Any time someone calls “crisis” I always ask “crisis for whom?”
Awesome, thanks for giving some clues. It’s a new build, but I didn’t focus hugely on RAM, I think it’s only 32GB. I’ll try this out.
Edit: I did some reading about L2ARC, so pending some of these tests, I’m planning to get up to 64gb ram and then extend with an l2arc SSD, assuming no other hardware errors.
They’re Seagate Exos, https://www.seagate.com/products/cmr-smr-list/ and appear to be CMR
Yes, and reading the parent I see they were speaking of exploiting laws, not people specifically. Thanks for clarifying, hope you have a nice day
I don’t know that I’d point to the security theater of TSA as an example of “doing it right”. But agreed, they have a better shot than Rite Aid.
I think the bigger problem is shoplifting is not a symptom of poor security, but rather poor society.
Lawful =/= non-exploitative
Reading further, walking is only counted at a 0.3 : 1 ratio of distance, for no conceivable reason. So you can run for ~12 minutes or walk for ~1 hr, it seems.
But why should my bonus be tied to something that is not at all related to my work? Should I get a pay cut if I eat a Dorito? Am I worthy enough of a pittance, CEO? Or should I be jumping through literal hoops?
First inter-user messaging was 62 years ago, first email client was 51 years ago, first spam was 45 years ago, first attachments were 31 years ago.
I don’t work with it directly, but it seems we’ve bolted on a lot of “fixes and functionality” onto email, but the underlying protocols haven’t changed dramatically.
And now nearly 56.5% of all emails were spam last year. Though I don’t think that counts intranet spam I get from my bosses all the time.
The Verge has staff on Mastodon for a while now.
Is this an article for staff of The Verge? Or is it for an audience that might only relate to something if it’s connected to something they’ve heard of?
Not having a central authority means you have no real power to stop someone
This is demonstrating the exact opposite. Community organization is valid.
It appears active users is the default status, at least as of this post.
Be the change you wish you see in the world. :)