Bug 114672 - [PATCH] Fix warning when trying to remove VMware lock files
Summary: [PATCH] Fix warning when trying to remove VMware lock files
Status: CLOSED DUPLICATE of bug 110265
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: initscripts
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-30 21:58 UTC by Felipe Alfaro Solana
Modified: 2014-03-17 02:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 19:01:01 UTC

Attachments (Terms of Use)
Fix warning when trying to remove VMware lock files (343 bytes, patch)
2004-01-30 22:02 UTC, Felipe Alfaro Solana
no flags Details | Diff

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):

How reproducible:
As long as initscripts is mantained

Steps to Reproduce:
Actual results:

Expected results:

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:

    --- 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
Better now? 

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.

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