Bug 66040 - Problem extracting socket file types from binary RPMs.
Summary: Problem extracting socket file types from binary RPMs.
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-06-04 21:22 UTC by Sam Varshavchik
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-06-04 21:37:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Sam Varshavchik 2002-06-04 21:22:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205

Description of problem:
rpm properly packages inodes of type __S_IFSOCK, but upon installation, a junk
file is left in place instead of the actual socket node.

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

How reproducible:

Steps to Reproduce:
1.  Build a dummy RPM with the following:


mkdir $RPM_BUILD_ROOT/tmp

perl -e "use Socket;

socket(x, PF_UNIX, SOCK_STREAM, 0);
bind(x, sockaddr_un('$RPM_BUILD_ROOT/tmp/sock'));



2.  Install the resulting binary RPM


Actual Results:  You'll end up with /tmp/sock;af76e65c, or something similar.

Expected Results:  /tmp/sock

Additional info:

Comment 1 Jeff Johnson 2002-06-04 21:30:40 UTC

There's simply no reason at all to put socket types in

Don't you have something better to do?

Comment 2 Sam Varshavchik 2002-06-04 21:37:23 UTC
The socket file, created by the application, gets tracked in the rpm database
just like any other file, and automatically removed when the application is

Comment 3 Jeff Johnson 2002-06-04 21:47:50 UTC
Files "created by an application" don't belong
in packages.

Leave it alone, please.

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