diff options
author | Dave Brolley <brolley@redhat.com> | 2009-12-21 20:37:01 -0500 |
---|---|---|
committer | Dave Brolley <brolley@redhat.com> | 2009-12-21 20:37:01 -0500 |
commit | 0f4e0b6fed0ee334cf33073be381ee22925b59a7 (patch) | |
tree | b776a0ff87d4c8c63f9c7473662a3090e10cf8a7 /NEWS | |
parent | e9fb9b955c80d8181e997bdd3477a52c4f34f0ce (diff) | |
download | systemtap-steved-0f4e0b6fed0ee334cf33073be381ee22925b59a7.tar.gz systemtap-steved-0f4e0b6fed0ee334cf33073be381ee22925b59a7.tar.xz systemtap-steved-0f4e0b6fed0ee334cf33073be381ee22925b59a7.zip |
NEWS entry for client/server/cert tools reorg.
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -18,6 +18,20 @@ See initscript/README.stap-server for details. +- Some of the of the compile server client, server and certificate + management tools have been moved from $bindir to $libexecdir/systemtap. + You should use the new stap-server script or the stap-server initscript + for server management where possible. The stap-server script provides the same + functionality as the stap-server initscript except that the servers are + run by the invoking user by default as opposed to servers started by the + stap-server initscript which are run by the user stap-server + by default. See stap-server(8) for more information. + + You may continue to use these tools by adding $libexecdir/systemtap to + your path. You would need to do this, for example, if you are not root, + you want to start a compile server and you are not running systemtap from a + private installation. In this case you still need to use stap-start-server. + - Any output line that starts with "ERROR", as in error("foo"), will promote a "Pass 5: run failed", and the return code is 1. |