Whoops, that's a thinko, this really does work: find / -type l ! -path '/proc*' -exec file {} \; | grep "broken symbolic"
I hope you don't mind a patch :)
find / -type l -path '/proc' -prune -o -exec file \{\} \;|grep "broken symbolic" > broken.links
This gets rid of all those /proc entries that you don't want to see or mess with.
--Jeremy
To findbroken links I used (with help from a good find man):
find / -type l -exec file \{\} \;|grep "broken symbolic" > broken.links
Run as root that will list them all in broken.links
On Wed, 24 Jan 2001, you wrote: > On 22 Jan, Richard Smith wrote:
The answer is that I have a /tmp partition (shared with another distribution), and my /var is actually a link to /tmp/VAR.SuSE. So the REAL path to /etc/texmf.cnf needs an extra ../ to get back to / and thence to /etc. "find" showed up many other broken links, broken for the same reason. ... 3. (Extra) How many installations are in the same boat?
I've had the same problem with /opt. On my system, /opt is a symlink to /usr/opt. Relative symlinks under /opt (like those in GNOME) break with every upgrade. Took me two weeks to solve it the first time. Now I just remember to fix them after upgrading...
Personally, I wish packagers would use absolute paths with symlinks. Or at least with the links that go back to /.
What 'find' command did you use to get broken links?
-- Robert Wohlfarth rjwohlfar@bigfoot.com
"Is not life more important than food, and the body more important than clothes?" -- Matthew 6:25b
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq