noobrants

5y

Me: kills process
Linux: 3243 killed.
Me: "sudo netstat -ntlp | grep 3243"
Linux: 3243 running.
* hour later *
Me: kills process with 3045974th method
Linux: 3243 killed.
Me: "sudo netstat -ntlp | grep 3243"
Linux: 3243 running.
Me: "Are you absolutely FUCKING kidding me?! What is this fucking thing, the god damn grim reaper? I've done some SKETCHY fucking things at the terminal to kill this BASIC fucking server and it is still running!! WHAT THE FUCK ARE YOU?!"
Manager: peeks in helpfully "Did you try the 'kill' command?"

devrant

linux

Ranter

Comments

7

bahua

13139

5y

sudo kill -9 <PID>

?
10

netikras

34513

5y

Checking processes with netstat... That's interesting 😁
3

noobrants

650

5y

@netikras local server, didn't need all the results from ps
3

noobrants

650

5y

@bahua also didn't work - it's dead now, but it took way too long
1

netikras

34513

5y

@noobrants kill -9 didn't work?? Then your storage devices might be fucked up
6

noobrants

650

5y

@netikras will never know probably - i just rebooted and then it was no longer running. The very sophisticated "turn it off and on again" technique I developed.
1

netikras

34513

5y

If you storage is indeed fkd up you WILL know
2

shaji

1252

5y

Probably respawned
2

mundo03

5023

5y

I had this with unicorn, there is a master process spawning processes when they die
0

Cybork

1055

5y

-i :port
1

Root

82997

5y

Them undead processes
8

DataJockey

1177

5y

plot twist, process 3243 was netstat.
1

Cybork

1055

5y

@DataJockey was actually expecting this
0

DataJockey

1177

5y

@Cybork exactly, me2
0

onethread

668

5y

Maybe a service restarted automatically by systemd or similar?

Related Rants

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service