This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

SystemTapGui usage scenarios.


Listing the usage scenarios i can think of for stapgui. Please add to the list if i have missed something.

1. Client and Server running on the same local machine(a laptop?). In this scenario a hard-dependency on the compile-server might not be a good idea. The systemtap installation on the m/c would have the compile-server scripts, but ideally the compile-server will not be registered as a service in this case.
2. Client and server on different machines in a cluster environment. A lean server that only does execution with the compile-server taking care of compilation would be a good option, esp if the server does not have the required dependencies like debuginfo setup.
3. A lean server, with the client doing the compilation and sending over the module to the server. The client and server would need to have an identical setup.
4. The client , server and compile-server all on the same machine (possibly in a clustered environment) with the m/c running the server also running the compile-server service.
5. The client running on a windows box. In this scenario access to the server's systemtap installation would be needed to list probes/functions and for syntax-checking.
6. Multiple servers with a single client.


Regards,
Anithra.




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]