Broken symlinks

[0001]

I have always wanted to ask this, but never thought about it before when logged in to the forum.

The directory:

/home/user/.config/vivaldi/

contains three symlinks:

SingletonCookie -> nnnnnnnnnnnnnnnnnnn
SingletonLock -> systemname-nnnn
SingletonSocket -> /tmp/..com.vivaldi.Vivaldi.xxxxx/SingletonSocket=

The destinations of the first two of those do not exist (with the directory listing of them appearing in red).

The listing of the directory referenced in the third symlink contains two entries:

SingletonCookie -> nnnnnnnnnnnnnnnnnnn
SingletonSocket=

The first (another non-existent destination) repeats the number of the cookie in the profile directory.

The second shows an actual socket.

Since broken symlinks usually indicate that something has gone wrong, I wonder:

1. Has something gone wrong specific to my setup?

2. What purpose(s) do the cookie and lock (which don't exist) have?

3. With a possible answer to question 2 of "obviously, nothing too important," why do these broken entries get created in the first place?

[Pathduck]

@0001 A little searching finds me:
https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/process_singleton_posix.cc
Like a lot of Chromium stuff, this is not documented anywhere but in the source.

I guess someone actually on Linux will have to say if this is normal or not.

[mib2berlin]

@0001
Hi, they are "normal" in a Linux install.
I cant say what they are doing in Vivaldi but locking on Linux is only one process can access a file at the same time.

Cheers, mib