ls -alR /proc/*/exe 2> /dev/null |
grep deleted
lrwxrwxrwx 1 brent            brent            0 Jun 19 06:13 /proc/1243/exe -> /usr/bin/wireplumber (deleted)

related to wireplumber update?
[ @Axios cleaned old documents and found one you posted long ago called Sandfly Sec. commands. this is one of them]

  • Axios replied to this.

  • brent That command is not in the ones I use but did run it mine came back with nothing
    So I cant say whats going on if you just did an update or something I would reboot.
    I did do the wire plumber update awhile back.
    Didnt explore everything with that website was alot info.

      brent That command is not in the ones I use but did run it mine came back with nothing
      So I cant say whats going on if you just did an update or something I would reboot.
      I did do the wire plumber update awhile back.
      Didnt explore everything with that website was alot info.

          Axios well I did my update this morning for wireplumber and did not reboot yet. this is common sometimes where it might be running in memory. I will reboot and set you as best answer.

          PS---that command sheet implied having 0kb logs was suspicious ("Check for zero size logs:
          ls -al /var/log/*") and I have a bunch of them...you can really rile yourself up if you don't know what you are looking at or why 🙂 (that's me for stuff like this)...thanks for checking, also. edit: sp

            brent Not that you had a problem but shows prob a person should reboot anyways
            after updates.
            Its a habit I do from winders days.

                Axios I reboot 99 times out a 100 but did not that day. I guessed the deleted file was still running in memory but you confirmed it. Yes, windows habits. Remember those gigantic KB package nightmare updates? Ugh