source: branches/development-0.7-arm2/NEWS @ 704

Revision 369, 5.5 KB checked in by dcarter, 4 years ago (diff)

merge of development-0.6 branch

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