Mysterious file socket
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Hi all,
After booting my system, I find a mysterious file socket in /tmp with a name that has all sorts of non-printable characters:
ls /tmp/d^M�^N\:���e��Z�eg��\}��+\&X즜\?W�q\@P
'/tmp/d'$'\r''�'$'\016'':���e��Z�eg��}��+&X즜?W�q@P'
It's not in use anymore by the time I find it. Does anybody have any idea how I could figure out where it is coming from?
Many thanks in advance!
A good start would be to discover what command is associated to the file, by executing in a terminal:
$ lsof +c 0 /tmp
When I run that command, there is no output. It seems the file socket is created at boot-up but afterwards program responsible for its creation stops using it.
I too get nothing with that command. Try adding '/*' after tmp. My computer results in one file although there are others.
# lsof +c 0 /tmp/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ksmserver 1076 eric 17u REG 8,4 434 2097184 /tmp/ksmserver.ztHBUQ
Yes, for me it's similar:
$ lsof +c 0 /tmp/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ksmserver 2041 julius 17u REG 253,2 414 1048581 /tmp/ksmserver.MsJKmw
$ ls -lh /tmp/d^M�^N\:���e��Z�eg��\}��+\&X즜\?W�q\@P
srwx------ 1 julius julius 0 aug 2 18:02 '/tmp/d'$'\r''�'$'\016'':���e��Z�eg��}��+&X즜?W�q@P'
$ lsof +c 0 /tmp/d^M�^N\:���e��Z�eg��\}��+\&X즜\?W�q\@P
I think lsof can only observe the current state and not the prior state. Maybe I can replace that socket with a file or directory that's read-only and observe if anything fails.
Alright, I found out at least that this file socket appears each time I start Jami!
I'm using the version from the Trisquel repositories (which I understand is a bit dated). Did nobody else see this?
Sounds like that is where the file is from. I started Jami and too noticed a strange file in my /tmp/.
Installing the latest version from their site still results in that file being created!!