51
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
Resolved Caveats
Resolved Caveats - Release 3.0(6)
Table 6
lists and describes Caveats that were resolved in Cisco CallManager
Release 3.0(6)
Note
If you have an account with Cisco.com (Cisco Connection Online), you can
use the Bug Toolkit to find caveats of any severity for any release.
To access the Bug Toolkit, log on to
http://www.cisco.com/support/bugtools.
.
Table 6
Cisco CallManager Release 3.0(6) Resolved Caveats
DDTS Number Summary
Explanation
CSCdr22835
Users cannot change WS-X6608 port
type once set without resetting card
Cisco CallManager software was changed
to find the correct WS-X6608 port type.
CSCdr74342
DCD: DC Directory gets suspended due
to FileSystem error
The problem was due to the file system
backup utility locking the file using the
win32 LockFile(). LockFile either allows a
shared Read lock or an exclusive Read or
Write lock. If a shared Read lock has been
obtained by a process; no process
(including the one that had first opened the
file) can write to that file. Thus, if a user
attempted to update DCD while the backup
utility held a lock on DCD's DB volumes,
DCD was unable to write to disk and
consequently got into an awkward state.
DCD now obtains an exclusive Read/Write
lock on startup on its DB volumes. This
lock prevents any other process from even
opening the file. Thus, DCD is guaranteed
that no process can deny it (DCD) write
access to its own files once it (DCD)
successfully comes up.
