byteman workflow

[judovana]

major - after every "from jrd" byteman install, attach second "after byteman agent" and - major - create remote vm for it, which is saved - major - as "after byteman PID JRD agent for bytman on PORT" or simialrly, as that will be used for checking if this agent exists or notm and what port it is on.

two cases

• local or no vm is selected - no ability to submit install/submit/unsubmit
• for remote - if it is "our bytman" agent, then it have port in name, otherwise IDK
• if it is local vm then - check if there is byteman agent - chcheck by byteman/our artificial after bytmean agent then offer submit/unsubmit
  • if there is no agent, offer install

[judovana]

second JRD agent is not honoring original agent, but is reporting itself

[judovana]

implemented in 8.0