this post was submitted on 16 Sep 2024
754 points (99.5% liked)

Lemmy Shitpost

26892 readers
1951 users here now

Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.

Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means:

-No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.


Also check out:

Partnered Communities:

1.Memes

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

6.You Should Know

7.Comedy Heaven

8.Credible Defense

9.Ten Forward

10.LinuxMemes (Linux themed memes)


Reach out to

All communities included on the sidebar are to be made in compliance with the instance rules. Striker

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] henfredemars@infosec.pub 53 points 2 months ago (4 children)

I have encountered processes that even Task Manager could not kill.

[–] wesker@lemmy.sdf.org 39 points 2 months ago* (last edited 2 months ago) (3 children)

All the damn time. I typically use Linux, so having a process I can't even force kill is a severely annoying concept.

[–] henfredemars@infosec.pub 32 points 2 months ago* (last edited 2 months ago) (3 children)

This has happened to me only once on Linux. I still tell stories about it.

It was a CD burning program stuck in uninterruptible sleep! Trapped in a system call into the kernel that can never be interrupted by a signal, it was truly unkillable. The SIGKILLs simply piled up never to be delivered.

[–] Lost_My_Mind@lemmy.world 19 points 2 months ago (2 children)

THIS is your big "You won't believe what happened to me...." story???

sigh

When I was 14, I took the power cord for the original PS1 and shaved the rubber off the end until metal prongs were sticking out. Then I noticed if the outlet end was plugged in, and you touched the metal prongs on the other end, you couldn't drop it. It would electricute you, but it would also stick to your skin for 5-10 seconds as it electricuted you.

So being a 14 year old male, I did the only logical thing. I put it on my penis.

It was quite shocking!

[–] henfredemars@infosec.pub 14 points 2 months ago (1 children)

I used to stick forks in the electrical outlets.

Now I post Linux memes.

[–] Lost_My_Mind@lemmy.world 6 points 2 months ago
[–] Honytawk@lemmy.zip 1 points 2 months ago

I can't believe what happened next

[–] lolrightythen@lemmy.world 11 points 2 months ago (1 children)
[–] Lost_My_Mind@lemmy.world 9 points 2 months ago (2 children)

I....can't tell what is happening here. Is he having an orgasm? Is he supposed to be a priest, or a slave?

That's Frodo Baggins on the verge of death thou fool!

[–] lolrightythen@lemmy.world 1 points 2 months ago

I don't recall. Just having fun. Be well!

[–] Ziglin@lemmy.world 3 points 2 months ago (1 children)

I would assume that was a kernel issue.

[–] henfredemars@infosec.pub 3 points 2 months ago* (last edited 2 months ago)

In this case it was a driver holding that thread captive and making an assumption about the hardware eventually responding to a request which never completes.

So yes indeed it was the kernel, and ideally the driver could be written better, but that’s probably easier said than done when the hardware can do weird things.

This was a long time ago, so for all I know the issue has been long corrected.

[–] laranis@lemmy.zip 2 points 2 months ago

It honestly was the thing that pushed me to Linux. Once I could no longer kill programs at-will I couldn't handle it. xkill ftw.

[–] nickwitha_k@lemmy.sdf.org 1 points 2 months ago

Yeah... It doesn't happen often and when it does, it's usually a driver and/or hw issue that is likely to leak memory and/or hold file descriptors but procs in D (uninterruptible_sleep) state do happen. It's really obnoxious that murdering them with SIGKILL does nothing.

[–] SpicyLizards@reddthat.com 9 points 2 months ago

But I also remember the times when there was no foe Task Manager could not kill.

[–] Magikjak@lemmy.world 9 points 2 months ago (1 children)

A while ago I kept a shortcut in the taskbar that ran a batch file that killed any unresponsive task, worked even on those tasks that Task Manager can’t seem to close. As long as explorer was still running and I could alt tab and press that button it worked 100% of the time

[–] henfredemars@infosec.pub 8 points 2 months ago (1 children)

How do you determine if a task is unresponsive?

[–] Magikjak@lemmy.world 7 points 2 months ago (1 children)

It was something like this. It would just kill all tasks that haven’t responded in X amount of time. Obviously this is not a great solution as it can cause data loss and you could accidentally close more than just the program you intend to close, but sometimes you have little choice.

https://superuser.com/questions/1432304/how-can-i-automatically-kill-unresponsive-apps-and-games-with-a-batch-file

[–] flambonkscious@sh.itjust.works 4 points 2 months ago (1 children)

That's proper mental, I don't know why you'd keep that running unnecessarily (unless fiddling with something you can easily replicate).

Im pretty sure it's still not going to catch the stuck things that aren't actually killable

[–] Magikjak@lemmy.world 4 points 2 months ago

It wasn’t something I kept running, just a shortcut that would run the batch file and kill anything that wasn’t responding at the time. I’m not sure if this uses the same command I had set up at the time, but I remember it having a 100% success rate. I had it for one game in particular which would crash and stop responding but any attempts to get to the task manager (even with keyboard) would fail.

I haven’t had to use anything like this since Windows 10 as now you can just press Windows+Tab and move the task to a different desktop and then get into the task manager on your original desktop.

[–] aeronmelon@lemmy.world 1 points 2 months ago

“This computer is hereby deconstituted.”