|Summary:||[PATCH] Fix warning when trying to remove VMware lock files|
|Product:||[Retired] Red Hat Raw Hide||Reporter:||Felipe Alfaro Solana <felipe_alfaro>|
|Component:||initscripts||Assignee:||Bill Nottingham <notting>|
|Status:||CLOSED DUPLICATE||QA Contact:||Brock Organ <borgan>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2006-02-21 19:01:01 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Felipe Alfaro Solana 2004-01-30 21:58:55 UTC
Description of problem: ----------------------- This bug report is intended as a placeholder to store patches for inclusion in future releases of initscripts. Currently, I've got one patch against initscripts to fix a warning during boot when trying to remove lock files for VMWare. Version-Release number of selected component (if applicable): 7.44-1 How reproducible: As long as initscripts is mantained Steps to Reproduce: N/A Actual results: N/A Expected results: N/A Additional info: Until a CVS server is available for us, I think we should keep track of patches and ideas under this bug entry. However, if I'm wrong, please feel free to close this bug report.
Comment 1 Felipe Alfaro Solana 2004-01-30 22:02:47 UTC
Created attachment 97378 [details] Fix warning when trying to remove VMware lock files This fixes the warning that is shown during boot when rc.sysinit tries to remove VMware lock files. However, VMware organizes locks by user, then by PID and thus, what we're trying to remove is a directory and not a file. For example: /var/run/vmware | --- user1 | --- 12345
Comment 2 Bill Nottingham 2004-01-30 22:08:01 UTC
Why not add the 'Patch' keyword to such bugs instead?
Comment 3 Felipe Alfaro Solana 2004-01-30 22:18:12 UTC
Comment 4 Bill Nottingham 2004-01-30 22:20:33 UTC
No, what I'm saying is rather than have one placeholder bug which can never be closed, to just add the patch *keyword* (see: https://bugzilla.redhat.com/bugzilla/describekeywords.cgi) to each bug that has a patch.
Comment 5 Leonard den Ottolander 2004-02-05 14:23:17 UTC
Bug #110265 seems to be a duplicate of this one (or the other way round).
Comment 6 Bill Nottingham 2004-02-05 15:19:52 UTC
*** This bug has been marked as a duplicate of 110265 ***
Comment 7 Red Hat Bugzilla 2006-02-21 19:01:01 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.