ɐɥO@lemmy.ohaa.xyz to linuxmemes@lemmy.world · 2 years agoYou shouldlemmy.ohaa.xyzimagemessage-square97fedilinkarrow-up1701arrow-down136
arrow-up1665arrow-down1imageYou shouldlemmy.ohaa.xyzɐɥO@lemmy.ohaa.xyz to linuxmemes@lemmy.world · 2 years agomessage-square97fedilink
minus-squareFlax@feddit.uklinkfedilinkEnglisharrow-up10·2 years agoDoes this damage the computer? Or can it be fixed with a restart
minus-squarehglman@lemmy.mllinkfedilinkEnglisharrow-up18·2 years agoYou just have to restart somehow.
minus-squareacockworkorange@mander.xyzlinkfedilinkarrow-up5·2 years agoInvoke Palpatine to restart somehow.
minus-squareWhiskyTangoFoxtrot@lemmy.worldlinkfedilinkarrow-up3·2 years agoExecute order shutdown -r now?
minus-squareMacN'Cheezus@lemmy.todaylinkfedilinkarrow-up7·2 years agoNo, it’ll just lock it up but shouldn’t cause any damage or data loss unless you have unsaved work open. A restart should fix it.
minus-squareABeeinSpace@lemmy.worldlinkfedilinkEnglisharrow-up1·2 years agoNo. The effects of a fork bomb are temporary and are fixed with a restart
Does this damage the computer? Or can it be fixed with a restart
You just have to restart somehow.
Invoke Palpatine to restart somehow.
Execute order
shutdown -r now
?No, it’ll just lock it up but shouldn’t cause any damage or data loss unless you have unsaved work open. A restart should fix it.
No. The effects of a fork bomb are temporary and are fixed with a restart