## +24 ## Many Ways to Kill an Orc (or a Hero) ## PATRICE ROY 20 24 September 15 - 20 # Many ways to kill an Orc (or a Hero) Patrice Roy, Patrice.Roy@USherbrooke.ca, Patrice.Roy@clg.qc.ca ## From

Processes in Linux How to view all running processes? How to find a particular process? How to kill/stop a particular process? ☐ Finding out list of open files o Signals • top command ○ Load average tool. We will learn more about grep in the future. ## How to kill/stop a particular process? We can kill/stop any process using the kill command. We found out, in the last example, that the id of the the Firefox process in my computer is 26752, we can use that id to kill it. $ kill 26752 If there is no error message, you’ll find that Firefox has disappeared. ## Finding out list of open files Isof

courses for high schools this.explosionSound.play(); //player explosion will be added here this.player.kill(); this.game.time.events.add(800, this.gameOver, this); }, ## Particles and Game Over When you hit setTo(200, 200); 10 emitter.gravity = 0; 11 emitter.start(true, 1000, null, 100); 12 this.player.kill(); 13 14 // call the gameOver method in 800 milliseconds, we haven't created this method yet Online courses on Phaser and game programming Zenva for Schools – Coding courses for high schools Kill the player spite as well and call a gameOver method after 0.8 seconds (800 milliseconds), which we

SIGABRT, Aborted. ___pthread_kill_implementation (threadid=281474842450080, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory SIGABRT, Aborted. ___pthread_kill_implementation (threadid=281474842450080, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/ pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory SIGABRT, Aborted. ___pthread_kill_implementation (threadid=281474842450080, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/ pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory

chmod • 29. umask • 30. du • 31. df • 32. basename • 33. dirname • 34. ps • 35. top • 36. kill • 37. killall • 38. jobs • 39. bg • 40. fg • 41. type • 42. which • 43. nohup • 44. xargs namelnpssleepunlinkchmoddfkilllspwdsttywait4pathcpechoks process ID. This is key when you want to reference this process in another command, for example to kill it. Then we have TT that tells us the terminal id used. Then STAT tells us the state of the process:

transports) json_loads()_(socketio.virtsocket.Socket_static_method) ## K kill().(socketio.virtsocket.Socket method) kill local jobs().(socketio.namespace.BaseNamespace method) ## L lift acl restrictions() # error, so let's just let it go, and not kill # socket completely. Other processes will # we kill everything if the user expires the actually). This will trigger an onDisconnect() call on the client side. Over here, we will kill all `spawn`'ed processes and remove the namespace from the Socket object. for a spawned

|unique\_id| |---| |diff| |echo| |chown| |chmod| |mask| |du| |df| |basename| |dirname| |ps| |top| |kill| |killall| |jobs| |bg| |fg| |type| |which| |nohup| |xargs| |vim| |emacs| |nano| |whoami| |who| |su| process ID. This is key when you want to reference this process in another command, for example to kill it. Then we have TT that tells us the terminal id used. Then STAT tells us the state of the process: by memory utilized: top -o mem ## kill Linux processes can receive signals and react to them. That's one way we can interact with running programs. The kill program can send a variety of signals

ontainer/K8s|K8s|K8s| |CPU burn|✓|✓|✓|✓|✓| |Mem burn|✓|✓|✓|✓|✓| |container kill|✓|✓|✓|✓|✓| |pod failure|✓|✓|✓|✓|✓| |pod kill|✓|✓|✓|✓|✓| |network partition|✓|✓|✓|✓|✓| |network duplication|✓|✓|✓|✓|✓| |network fill|✓|✓|✓|✓|✓| |Disk loss|✓|✓|✓|✓|✓| |Time skew|✓|✓|✓|✓|✓| |Kernel chaos|✓|✓|✓|✓|✓| ● PodChaos: kill / fail / container/... ● NetworkChaos: delay / lose / dup / partition / ... IOChaos: latency / fault KernelChaos: kernel fault injection ● StressChaos: burn cpu and memory ☑ DNSChaos .... pod-fail container-kill network-loss Io-delay lo-erno YAML ![Image](/uploads/documents/a/6/4/f/a64f2a1b9a259d779bfeba7888af7c5c/p15_2

• Hypothesis TiDB uses Raft consensus algorithm to replicate data and provide fault-tolerance o Kill one TiDB instance, if the instance has a leader replica, the QPS may drop because the client can’t leader soon to service the client’s write again ☐ The QPS will be recovered ## • Run experiment ☐ Kill one TiDB instance randomly ## • Verify ☐ The QPS dropped but not recovered anymore ☐ A bug is found loss duplication corrupt partition STRESS io-latency io-fault attr-override pod-kill pod-failure container-kill DNS KERNEL clock-skew cpu-burn memory-burn kernel-inject dns-random dns-fail

view all running processes? ..... 37 7.2 How to find a particular process? ..... 37 7.3 How to kill/stop a particular process? ..... 38 7.4 Finding out list of open files ..... 38 7.5 Signals ... We will learn more about grep in the future. ### 7.3 How to kill/stop a particular process? We can kill/stop any process using the kill command. We found out, in the last example, that the id of the the Firefox process in my computer is 26752, we can use that id to kill it. $ kill 26752 If there is no error message, you’ll find that Firefox has disappeared. ### 7.4 Finding out list of open files