Difference between revisions of "Cartographer Project Release Notes"
From Krupczak.org
(→Known Issues) |
|||
| Line 19: | Line 19: | ||
* New and improved Windows Vista ''security'' makes running ''ntsetup'' and ''cartographertray'' a real chore. | * New and improved Windows Vista ''security'' makes running ''ntsetup'' and ''cartographertray'' a real chore. | ||
| + | |||
| + | * Automatic upgrades sometimes (very rarely) fail because agent engine takes too long to stop and re-start. | ||
| + | |||
| + | * Windows use of reserved ports during dynamic binding fools some dependency determination. For example, an application may ask for a dynamically-bound TCP port and be assigned the well-known and/or reserved port of 1812 thus triggering a false ''Radius'' dependency. | ||
| + | |||
| + | * Dependencies determined via TCP port allocation may be missed of the connections are short-lived. | ||
| + | |||
| + | * XML DTDs or Schemas are needed for XMP and MIBs. | ||
| + | |||
| + | * IPv6 support '''is''' included but still needs more work with respect to DNS. | ||
Revision as of 15:32, 11 November 2008
Cartographer Project Release Notes
Release 1
The first, initial release consists of the following components/versions.
- Cartographer GUI version 0.27
- Agent engine (xmpd) version 0.72
- MIB2 plugin version 0.91
- Cartographer plugin version 0.41
Known Issues
- Some default installations of 64-bit Linux do not automatically include 32-bit versions of libxml and libz and thus need to be installed by hand.
- Some default installations of 64-bit Linux do not automatically include a 32-bit libgcc_s which is required by pthreads_cancel(). If not present, the library can be installed by hand.
- Occasional segmentation-fault on UNIX.
- New and improved Windows Vista security makes running ntsetup and cartographertray a real chore.
- Automatic upgrades sometimes (very rarely) fail because agent engine takes too long to stop and re-start.
- Windows use of reserved ports during dynamic binding fools some dependency determination. For example, an application may ask for a dynamically-bound TCP port and be assigned the well-known and/or reserved port of 1812 thus triggering a false Radius dependency.
- Dependencies determined via TCP port allocation may be missed of the connections are short-lived.
- XML DTDs or Schemas are needed for XMP and MIBs.
- IPv6 support is included but still needs more work with respect to DNS.
