This happend to me right noww as I tried to write a gui task manager for the GNU/Linux OS

  • CameronDev
    4·
    2 months ago

    Ah, that definitely would feel like a crash. Sent kill signal to cgroup accidentally? Or just iterate over all processes and signal them all?

    • bi_tux@lemmy.worldOP
      6·
      2 months ago

      probably the later, but idk how, all I did was insert a string in the following command like this:

      ``Command::new(“bash”)

      .arg(“-c”) .arg(format!(“ps -aux | grep -i "}" awk '{{print $2}’ | xagrs kill -9”, input)

      .output()

      .expect(“error”);``

      I’ve tested the command and it worked flawlessly in the terminal, but I have no idea what I’m doing, since I’m new to rust and never worked with this library

      • CameronDev
        7·
        2 months ago

        There are rust libraries to send signals, might be better to use those rather than calling bash. eg. https://docs.rs/nix/latest/nix/sys/signal/index.html

        I’m guessing if input was “”, then it would sigkill all processes? Less confident, but some functions behave slightly differently in an interactive console vs a non interactive, maybe ps has a different format when used non interactively?

        Aside, you want three backticks and a newline to get code formatting :)
        • bi_tux@lemmy.worldOP
          5·
          2 months ago

          thx, btw I figured it out:

          I forgot to trimm the string, so it had a line break in it which lead to grep showing the processes from the term I put in + all processes that contain a space/linebreak and appearently all processes shown by ps aux contain some kind of space (makes sense, since there are spaces between the user, pid, etc) so yeah, I ended up trying to kill every process on the system, but it only killed the user processes, since I ran everything without sudo