I asked on stackoverflow for my problem. And i will ask here too…

Does anybody know, what the problem could be?

  • taladar@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    It is strange behaviour… a process unlinks a socket-file, which does not belong to him, only the name is the same

    That is what I would expect it to do actually. I would expect it to close the socket it has open and the delete (unlink) it by name.

    • Jakob :lemmy:@lemmy.schuerz.atOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      I expect, it deletes the socket, which on which the process is listening. what if i rename the socket (for some reason). Then the socketfile should be deleted also.

      • taladar@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 months ago

        Directory operations like unlinking (deletion) traditionally work via paths, not open file handles.