Hide Forgot
Description of problem: This is a Regression bug https://bugzilla.redhat.com/show_bug.cgi?id=598163 this bug fixed in rhel6.0 libvirt socket file still exist after remove libvirt package Version-Release number of selected component (if applicable): libvirt-0.9.3-8.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. install libvirt #yum install libvirt 2. start service # service libvirtd start # ll /var/run/libvirt/libvirt-sock srwxrwxrwx. 1 root root 0 Jul 26 15:19 /var/run/libvirt/libvirt-sock 3. removre libvirt #rpm -e libvirt 4. check socket file # ll /var/run/libvirt/libvirt-sock srwxrwxrwx. 1 root root 0 Jul 26 15:19 /var/run/libvirt/libvirt-sock it is still there . Actual results: After remove libvirt package ,the libvirt socket file still exist Expected results: After remove libvirt package ,the libvirt socket file should be deleted Additional info:
daemon: Unlink unix socket paths on shutdown This patch introduces a internal RPC API "virNetServerClose", which is standalone with "virNetServerFree". it closes all the socket fds, and unlinks the unix socket paths, regardless of whether the socket is still referenced or not. This is to address regression bug: https://bugzilla.redhat.com/show_bug.cgi?id=725702 Patch committed into upstream.
Reproduced this bug with libvirt-0.9.3-8.el6 and verified PASS with libvirt-0.9.4-2.el6.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1513.html