Bug 55139 - Dangling symlinks after RedHat Linux v7.2
Summary: Dangling symlinks after RedHat Linux v7.2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: foomatic
Version: 7.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact:
URL:
Whiteboard:
: 55914 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-26 04:52 UTC by Steve Snyder
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-10-26 04:52:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Steve Snyder 2001-10-26 04:52:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011013

Description of problem:
A scan for dangling symlinks finds 2 of them, both from the foomatic package.


Version-Release number of selected component (if applicable):


How reproducible:
Didn't try

Steps to Reproduce:
1. Install RedHat Linux v7.2, selecting the package set Everything.
2. After the initial boot of the system, run this:

    symlinks -tr / | grep dangling



Actual Results:  Two dangling symlinks were found:

dangling: /usr/share/foomatic/db/compiled -> /var/cache/foomatic/compiled
dangling: /usr/share/foomatic/db/pcache -> /var/cache/foomatic/pcache

Expected Results:  No dangling symlinks should be found.


Additional info:

Comment 1 Bill Nottingham 2001-10-29 19:19:34 UTC
They're created when printconf is first run, iirc.b

Comment 2 Bill Nottingham 2001-11-09 02:19:05 UTC
*** Bug 55914 has been marked as a duplicate of this bug. ***

Comment 3 Need Real Name 2002-02-26 16:08:17 UTC
I also have this problem.

System: RedHat 7.2.

As an extension, any symlink I (either manually of from a script) have created
since after completing the install, results in a dangling symlink.  Is it
possible there could be a problem with the ext3 drivers?

Comment 4 Steve Snyder 2002-02-27 01:57:06 UTC
The problem isn't ext3-specific.  I see it on ext2 filesystems.



Note You need to log in before you can comment on or make changes to this bug.