edit: fixed thumbnail

  • slazer2au@lemmy.worldEnglish
    144·
    10 months ago

    Network engineer who uses ISIS as a routing protocol on Huawei equipment. I assume I am on several.

  • GombeenSysadmin@lemmy.world
    88·
    10 months ago

    “If you are interested in getting help with child abuse, here are some resources”

    Hi ChildHelp, can you help me kick the shit out of some kids please?

  • Kaelygon@lemmy.worldOP
    493·
    10 months ago

    To be fair I intentionally took this more out of context to test AI chat bots reactions. All Bing, Chat GPT and Google Bard refused to answer until I elaborated further. I was looking into killing .exe programs when wineserver crashes and got side tracked to this. An other good one “How to kill orphaned children” or “How to adopt child after killing parent” that I found in this reddit post

      • Kaelygon@lemmy.worldOP
        151·
        10 months ago

        Interesting! I also noticed that search engines give proper results because those are trained differently and using user search and clicks. I think these popular models could give proper answer but their safety tolerance is too tight that if the AI considers the input even slightly harmful it refuses to answer.

        • Monkey With A Shell@lemmy.socdojo.com
          3·
          10 months ago

          Given some of the results of prior AI systems unleashed on the public once the more ‘eccentric’ parts of society got ahold of them that’s no surprise. Not only do they have to worry about the AI picking up bad behaviors but are probably looking out for ‘well this bot told me that it’s a relatively simple surgery so…’ style liabilities.

    • MonkderZweite@feddit.ch
      8·
      10 months ago

      Kill the exe process itself, killing wineserver doesn’t help, that spawns just new children. Similiar to goblins.

  • _edge@discuss.tchncs.de
    373·
    10 months ago

    I’m sorry, I cannot answer this question. ChatGPT is owned by Microsoft now. How dare you bring Linux to party?

  • LoveSausage@lemmy.ml
    181·
    10 months ago

    Just recently annotated possible child abuse on a client’s case. Lol, I did went back and edited it out after realising what I wrote.

  • dylanTheDeveloper@lemmy.world
    4·
    10 months ago

    I useally create an ownership tag if whatever language I use doesn’t have one so I can kill the child and it works it’s way up to the parent

  • rwhitisissle@lemmy.ml
    4·
    10 months ago

    Depends on whether or not you want to kill only the child processes of a parent process or if you want to kill the parent as well. To kill the parent and children, you can kill the entire process group, specifying the pgid in the kill command. To kill only the parent you can trap SIGTERM in the parent and then send SIGTERM to the process group.

      • okamiueru@lemmy.world
        3·
        10 months ago

        Processes can make their own processes. If you know of such a secondary process, you might still want to terminate the one at the top.

        Something like that?

      • rwhitisissle@lemmy.ml
        2·
        10 months ago

        Processes in most operating systems (I’ll use Linux, because it’s what I know and because…Lemmy) are organized in a tree like structure. There’s some initial very low level code used to start the OS, and every other process spawns from that, which is to say they tell the operating system “Hey, please make this process I’m gonna tell you about - allocate resources for it, etc.” The operating system creates it and binds that new child process to the first one. The process that spawned the other process is called its parent. The process that just got spawned is called a child. You could also call them root and leaf processes, I suppose, but nobody really does that. Sometimes you want to get rid of all the child processes a process spawns, but leave the running process intact. Sometimes you want to kill the process that spawned everything and also cleanup anything it might have created. There are lots of programming scenarios in which you might want to do either. It really depends on how your application is designed and what it’s doing.

        That all said, there’s a command in Linux called “kill” and you can tell it the process id, process group id, etc. to kill a process or a process group. You can also manipulate what are called SIGNALS. Signals are a whole thing in Linux. They’re basically small values you can send to processes at any time and the operating system forces the process to perform some action whenever it receives one of them. SIGTERM basically stands for “SIGNAL: TERMINATE PROCESS.” So if you “trap” the SIGTERM, you can basically tell the operating system - whenever this parent process receives a SIGTERM, ignore it. The other processes in the process group - the child processes - all terminate, though, when they receive it.