Red Hat Bugzilla – Bug 66040
Problem extracting socket file types from binary RPMs.
Last modified: 2008-05-01 11:38:02 EDT
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):
Steps to Reproduce:
1. Build a dummy RPM with the following:
perl -e "use Socket;
socket(x, PF_UNIX, SOCK_STREAM, 0);
2. Install the resulting binary RPM
Actual Results: You'll end up with /tmp/sock;af76e65c, or something similar.
Expected Results: /tmp/sock
There's simply no reason at all to put socket types in
Don't you have something better to do?
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
Files "created by an application" don't belong
Leave it alone, please.