Checking for broken links in directory structures
FSlint
The GUI-based FSlint [3] tool, which is based on the findbl
command-line tool (in the fslint package) belongs in the same category as symlinks
. If you call findbl
without any other parameters (or -d
), it searches the current directory for broken links and prints the matches one by one.
Listing 9 shows the result of the call, which is practically identical to those from Listing 2 and Listing 8. The behavior of findbl
becomes clear after a closer look: It is simply a shell script that relies on find
for searching.
Listing 9
findbl
01 $ /usr/share/fslint/fslint/findbl . 02 project/version2/data/dataset3 -> project/version1/data/dataset3
rmlint and chase
I combined the rmlint
[4] and chase
[5] tools as a final option. (Shredder, rmlint
's graphical front end, looked really great on the rmlint
website, but I could not reproduce it on Debian GNU/Linux 11.)
Similar to FSlint, rmlint
aims to find and clean up inconsistencies in entries in the filesystem, including detecting broken links. You can see the call to do this in line 1 of Listing 10.
Listing 10
rmlint and chase
01 $ rmlint -T bl -o pretty:stdout . 02 $ chase old 03 /project/version1
The -T
switch lets you select what rmlint
will look for; bl
is the abbreviation for "broken links." The -o
option determines the output format, and the pretty:stdout
value gives you a prettified display. Figure 2 shows a sample call in which rmlint
detects two broken links (and that's how it's supposed to be).
The chase
tool also performs an exciting task: It tracks down the file to which a symbolic link actually points. It returns 1
in case of an error if the reference target does not exist. Line 2 in Listing 10 shows the call to the old
reference from our example, and the result is the filename.
Avoiding Mistakes
How do you prevent the occurrence of broken links in the first place? Basically, the only advice here is to be more careful because (apart from the filesystem) there is no place where all the links are stored. I'm not aware of a service that checks in the background to make sure that links remain intact and warns you before you break a link.
It makes sense to check, with any of the tools discussed in this article, to see if symbolic links for a file exist before proceeding to delete the file. If you only have access to find
and readlink
, follow the steps shown in Listing 11. The call lists both components – the link and the link target – side by side. To do this, find
uses the -exec
option to echo the name and then display the link destination determined via readlink
.
Listing 11
find and readlink
$ find . -type l -exec echo -n {} "-> " ';' -exec readlink {} ';' ./project/version2/data/dataset3 -> project/version1/data/dataset3 ./project/old -> project/version1 ./project/current -> project/version2
Keep in mind that symbolic links can cross filesystem boundaries. Your only option is to check everything that is mounted in the filesystem.
« Previous 1 2 3 4 Next »
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
So Long Neofetch and Thanks for the Info
Today is a day that every Linux user who enjoys bragging about their system(s) will mourn, as Neofetch has come to an end.
-
Ubuntu 24.04 Comes with a “Flaw"
If you're thinking you might want to upgrade from your current Ubuntu release to the latest, there's something you might want to consider before doing so.
-
Canonical Releases Ubuntu 24.04
After a brief pause because of the XZ vulnerability, Ubuntu 24.04 is now available for install.
-
Linux Servers Targeted by Akira Ransomware
A group of bad actors who have already extorted $42 million have their sights set on the Linux platform.
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.
-
Canonical Collaborates with Qualcomm on New Venture
This new joint effort is geared toward bringing Ubuntu and Ubuntu Core to Qualcomm-powered devices.
-
Kodi 21.0 Open-Source Entertainment Hub Released
After a year of development, the award-winning Kodi cross-platform, media center software is now available with many new additions and improvements.
-
Linux Usage Increases in Two Key Areas
If market share is your thing, you'll be happy to know that Linux is on the rise in two areas that, if they keep climbing, could have serious meaning for Linux's future.
-
Vulnerability Discovered in xz Libraries
An urgent alert for Fedora 40 has been posted and users should pay attention.