Re: DNF Upgrade Cleanup Dangling Symlinks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/12/24 09:58, Samuel Sieb wrote:
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.

In my view they are showing poorly designed software, I can understand the Thunderbird lock symlinks as Thunderbird is currently running, but Firefox is not running and it is configured to not continue running background tasks after closure (I think that option is in firefox). The firefox lock is in the profile folder, but I don't understand the purpose of the lock as its existence doesn't stop the folder from being deleted. To me the existence of that lock after shutdown is an indication to me that the developer was being lazy and not properly cleaning up on normal shutdown.

regards,
Steve


Attachment: OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
_______________________________________________
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
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux