Skip to content

Distributed.Process.Management Toolset #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hyperthunk opened this issue Dec 18, 2012 · 1 comment
Closed

Distributed.Process.Management Toolset #100

hyperthunk opened this issue Dec 18, 2012 · 1 comment

Comments

@hyperthunk
Copy link
Member

In line with issue #97 there are times when you'd like to get an overview of running processes in your system. Issue #89 is already starting to provide some of the primitives required to achieve something like this. There are other things a system administrator might want to do, such as manually running exit to terminate on a given process, set up links/monitors or even manually injecting messages (although that last one's a bit far-out).

Whilst the idea behind Network.Transport.Management is just about providing an API so we can build tools, the tools for this feature already exist by and large (viz getProcessInfo, exit, kill, link, etc) so this issue is really about providing the actual tools themselves.

I suspect that a command line admin interface would be best suited to this, at least to begin with. Whether or not that is something that takes parameters and runs specific commands, or something more interactive is up for debate. Again, this is the kind of thing that makes administrators and tech support love rather than hate your application.

I suspect this should be a top level project. Whether it belongs here or bundled in with -platform is another thing to consider.

@hyperthunk
Copy link
Member Author

I suspect this should be a top level project. Whether it belongs here or bundled in with -platform is another thing to consider.

I'm going to jump in before anyone else! Thinking about it, this would sit better in -platform land, and might even warrant being in a separate repo by itself. I'm a bit dubious about creating zillions of separate repositories, because of the overhead of managing all the individual version numbers and dependencies. But I think this is definitely not core CH, so I'm going to pull it over to distributed-process-platform. Closing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant