• Ephera@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      31
      arrow-down
      2
      ·
      1 year ago

      Well, in this case, it was a graphical program that was doing it, and I really could’ve recognized that the file was being created by that. I had just kind of forgotten that I opened this graphical program a few days ago on a different workspace…

  • fraichu@lemmy.ml
    link
    fedilink
    arrow-up
    16
    ·
    edit-2
    1 year ago

    I’m curious you’d see it in ls -l Did inode change? I remember making the same mistake. I think everyone sees this sometime during the career

    • Ephera@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      19
      arrow-down
      1
      ·
      1 year ago

      The inode does change, yeah:

      The regular ls -l doesn’t show the inode on my system, though. I only realized it when I had assigned more permissions to the file and those got reset by deleting the file. The last-modified timestamp also gets updated each time, but I only spotted that afterwards…

  • Still@programming.dev
    link
    fedilink
    English
    arrow-up
    16
    ·
    1 year ago

    lsof is a good tool would recommend it whenever something weird is happen, tho you gotta be root for it

  • LazaroFilm@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    1 year ago

    Kinda similar. I remember having a file I could t delete. But I could move it to a new folder and delete that folder and the file would delete.

OSZAR »