On 12/6/24 2:53 PM, Stephen Morris wrote:
On 7/12/24 01:43, Barry Scott wrote:
On 6 Dec 2024, at 13:13, Tim via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I suppose there could be symlinks that don't point to something, now,
but might in the future? Or, normally do, but didn't at the time of
your test.
Seems that all the dangling symlinks on my KDE VM are owned by RPMs.
I ran this to find this out the state of symlinks:
sudo symlinks -r / | grep dangling | while read A B C; do echo $B; rpm
-qf $B; done | grep 'is not owned'
Thanks Barry. I have 3 dangling symlinks at the moment, and your script
says they are not owned by any package. Not being owned is not
surprising as all 3 are "lock files" for Firefox and Thunderbird both of
which are not rpm installed, they are both upstream daily versions of
the two applications. I was trying to understand the target of the
symlink, which in the case of these 3 symlinks begins with my local IP
address, being 192.168.1.109:+5960 (for firefox). So after a few tests
it has become obvious they are making use of what seems to be standard
Linux functionality, in that Linux allows the creation of symlinks
linked to non-existent locations.
Right. That's an example of what I meant by an application storing text
data in a symlink. Even if they were rpm installed, the lock files most
likely won't be owned by the rpm.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
