Closed Bug 114648 Opened 23 years ago Closed 22 years ago

file locking untested under win32

Categories

(Calendar :: Internal Components, defect)

Product:
Calendar
Component:
Internal Components
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: gray, Assigned: gray)

Details

win32 doesn't do the file locking test. I don't even know that the file locking works under win32. I think this is really a big concern though. I don't really see a case for multiple processes try to hit the files under win32.
This is John's.
Assignee: mikep → gray
Status: UNCONFIRMED → NEW
Ever confirmed: true
I think this bug is pretty severe if I understand it correctly, I could potentially corrupt the calendar files with multiple calendars open.
Severity: normal → major
Blocks: 161124
John, want to make a comment as this has been open for about a year with no feedback from you in this bug.
Default QA Contact for Calendar has changed. If you wish to remain the QA contact for this bug, feel free to change it back.
QA Contact: colint → brantgurganus2001
No longer blocks: 161124
I don't think we're going to get this fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
VERIFIED
Status: RESOLVED → VERIFIED
QA Contact: gurganbl → libical
Component: libical → Internal Components
The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!
QA Contact: libical → base
You need to log in before you can comment on or make changes to this bug.