| 1 | arm4 -- History of visible changes. |
|---|
| 2 | |
|---|
| 3 | Copyright (C) 2005-2008, David Carter <dcarter@arm4.org> |
|---|
| 4 | See the end for copying conditions. |
|---|
| 5 | |
|---|
| 6 | Please send arm4 bug reports to dcarter@arm4.org or use our |
|---|
| 7 | online system at arm4.org |
|---|
| 8 | |
|---|
| 9 | Version 0.7 beta 1 |
|---|
| 10 | |
|---|
| 11 | NOTE: This is a beta release! See arm4.org for known issues with this |
|---|
| 12 | version. |
|---|
| 13 | |
|---|
| 14 | Java has arrived! This version introduces a full implementation of the |
|---|
| 15 | Java languages bindings. See the standard for more details. |
|---|
| 16 | |
|---|
| 17 | Also, the license has now changed from GPL/LGPL to the Eclipse Public |
|---|
| 18 | License v1.0. Information on this license can be found at |
|---|
| 19 | http://www.eclipse.org/legal/epl-v10.html |
|---|
| 20 | |
|---|
| 21 | Version 0.6 |
|---|
| 22 | |
|---|
| 23 | This release improves the agent's stability, although that work is still |
|---|
| 24 | ongoing. It's definitely ready for the serious user, but probably more |
|---|
| 25 | the developer or tester than on a production system. A heavily stressed |
|---|
| 26 | system may still experience some agent crashes. That being said, it |
|---|
| 27 | is being used in production environments, but you've been warned. |
|---|
| 28 | |
|---|
| 29 | For now, the requirement for xmlrpc-c has been removed, as the XMLRPC |
|---|
| 30 | reporting system is far from ready. This may be brought back in the |
|---|
| 31 | future as reporting options are explored further. |
|---|
| 32 | |
|---|
| 33 | Tickets closed in this release: |
|---|
| 34 | |
|---|
| 35 | 29 Crashing clients can leave an open message queue |
|---|
| 36 | 32 Add ability to disable RPC server |
|---|
| 37 | 35 Daemon should not accept HUP signals while backing up, or before the db is initialized |
|---|
| 38 | 37 A daemon should be able to detect an already running instance and exit |
|---|
| 39 | 43 arm4.conf needs parameters to controll the Berkeley in memory transaction sizes |
|---|
| 40 | 8 Add data aging |
|---|
| 41 | 23 Parrameterize queue, shared memory, and db home paths |
|---|
| 42 | 33 External programs may crash during DB backup |
|---|
| 43 | 34 Utility programs should be able to specify an archive as a command line option |
|---|
| 44 | 36 Add option to arm4_collect to show what the current collection state is |
|---|
| 45 | 38 When shutting down a program, full message queues may prevent the -s command from getting through |
|---|
| 46 | 40 Integrate arm4_collect into arm4_control |
|---|
| 47 | 41 Builds on RH Enterprise WS 4 require _GNU_SOURCE defined |
|---|
| 48 | 42 Move arm4_daemon's --remove and --clean functionality to arm4_control |
|---|
| 49 | 47 error messages should use syslog facility |
|---|
| 50 | 18 Daemon should be able to operate in user space with configurable parameters |
|---|
| 51 | 46 running arm4_control wipe twice causes a segmentation fault |
|---|
| 52 | |
|---|
| 53 | Known Issues |
|---|
| 54 | |
|---|
| 55 | 1. The agent isn't ready for OS X due to some limitations in its pthreads |
|---|
| 56 | implementation. |
|---|
| 57 | 2. All authorized users are able to control the agent. This needs to be |
|---|
| 58 | restricted. |
|---|
| 59 | 3. Archive operations can report problems opening files. This can be |
|---|
| 60 | ignored. |
|---|
| 61 | 4. Under certain circumstances, a hung or aborted daemon can prevent an |
|---|
| 62 | instrumented application from continuing |
|---|
| 63 | |
|---|
| 64 | Version 0.5 |
|---|
| 65 | |
|---|
| 66 | This release makes a more complete agent. Most subbuffer types are |
|---|
| 67 | now supported, including user buffers, diagnostic buffers, and |
|---|
| 68 | user defined metrics. |
|---|
| 69 | |
|---|
| 70 | Performance has been improved using the Berkeley DB in-memory transaction |
|---|
| 71 | feature. This requires version 4.3 or later, so this is a change in the base |
|---|
| 72 | system requirements. The configuration program has been changed to reflect |
|---|
| 73 | this. |
|---|
| 74 | |
|---|
| 75 | There are some new and expanded tests in the test directory. This is the |
|---|
| 76 | first step in a validation test suite that will be expanded as development |
|---|
| 77 | goes on. |
|---|
| 78 | |
|---|
| 79 | A new debugging utility has been introduced. arm4_dump allows the developer |
|---|
| 80 | to view the contents of the repository database. This isn't meant to be a user |
|---|
| 81 | level tool. |
|---|
| 82 | |
|---|
| 83 | Tickets closed in this release: |
|---|
| 84 | |
|---|
| 85 | 28 arm4_report fails to report transactions on Solaris |
|---|
| 86 | 3 Add support for user-defined metrics |
|---|
| 87 | 24 Aliases should be at the library level, not the daemon |
|---|
| 88 | 22 Add ability to turn ARM collection on and off |
|---|
| 89 | 25 Add support for user buffers in transactions |
|---|
| 90 | 26 Add support for diagnostic details in transactions |
|---|
| 91 | |
|---|
| 92 | Known Issues |
|---|
| 93 | |
|---|
| 94 | In certain cases, program crashes involving programs linked with libarm4 |
|---|
| 95 | may leave an open unnamed message queue. This will need to be removed |
|---|
| 96 | manually, or it will linger until the next reboot. |
|---|
| 97 | |
|---|
| 98 | |
|---|
| 99 | Version 0.4 |
|---|
| 100 | |
|---|
| 101 | The primary purpose of this release was to add an XMLRPC |
|---|
| 102 | reporting interface that could be used by web management tools, |
|---|
| 103 | but along the way many core deficiencies were uncovered and fixed. |
|---|
| 104 | |
|---|
| 105 | The structure of the ARM library and daemon have changed with |
|---|
| 106 | all of the database accesses having moved from the library to |
|---|
| 107 | the daemon. This results in more IPC calls, but greatly improves |
|---|
| 108 | the stability of the agent. |
|---|
| 109 | |
|---|
| 110 | The daemon now contains an XMLRPC interface that is being used to |
|---|
| 111 | develop a web management interface. This interface should not be |
|---|
| 112 | considered stable and is very likely to change as development continues. |
|---|
| 113 | |
|---|
| 114 | Some of the options to the daemon have changed in name and/or function, |
|---|
| 115 | so please read the documentation before using. |
|---|
| 116 | |
|---|
| 117 | Tickets closed in this release: |
|---|
| 118 | |
|---|
| 119 | 13 Berkeley DB permission errors cause database corruption |
|---|
| 120 | 12 Add XMLRPC based reporting interface |
|---|
| 121 | 15 API calls should accept empty ids |
|---|
| 122 | 19 Need to exit gracefully when daemon is unable to create shared regions |
|---|
| 123 | 21 The -r option to arm4_daemon doesn't remove the message queue |
|---|
| 124 | 16 arm_register_application accepts blank names and names with trailing blanks |
|---|
| 125 | 17 The -r option to arm4_daemon doesn't remove the databases as advertised |
|---|
| 126 | |
|---|
| 127 | Known Issues |
|---|
| 128 | |
|---|
| 129 | The agent doesn't currently support user defined metrics. This is |
|---|
| 130 | targeted for the next release. |
|---|
| 131 | |
|---|
| 132 | In certain cases, program crashes involving programs linked with libarm4 |
|---|
| 133 | may leave an open unnamed message queue. This will need to be removed |
|---|
| 134 | manually, or it will linger until the next reboot. |
|---|
| 135 | |
|---|
| 136 | ------------------------------------------------------- |
|---|
| 137 | Copying information: |
|---|
| 138 | |
|---|
| 139 | Copyright (C) 2005-2006, David Carter <dcarter@arm4.org> |
|---|
| 140 | |
|---|
| 141 | Permission is granted to anyone to make or distribute verbatim copies |
|---|
| 142 | of this document as received, in any medium, provided that the |
|---|
| 143 | copyright notice and this permission notice are preserved, |
|---|
| 144 | thus giving the recipient permission to redistribute in turn. |
|---|
| 145 | |
|---|
| 146 | Permission is granted to distribute modified versions |
|---|
| 147 | of this document, or of portions of it, |
|---|
| 148 | under the above conditions, provided also that they |
|---|
| 149 | carry prominent notices stating who last changed them. |
|---|
| 150 | |
|---|
