Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tsm ("Tivoli Storage Manager" which is now "IBM Spectrum Protect") is
used by a single application (archives). The installation of the current
client with bee on all systems would be much more complex now than
it was in the past, because
there is now a plugin machinery where shared libraries get loaded
at runtime. So it is no longer trivial to see, which libraries are
needed. A complete installation, on the other hand, consists of about
600 files which seems to be kind of overkill when these files get
distributed to and backed up on each system.
the client maintains more "local" data like keys generated for the
client and certificates downloaded from the server. These maintained
files, of course, would need to be special handled, otherwise they
would be overwritten by the distmaster. This would require a lot of
reverse engineering to identify everything and special code to handle
it.
For our only application using tsm, I've created an installation
in its project directory (at
/confidential/archive/tsm
). The tsm backupand archive client is no longer needed in the system.
So remove it. It is a binary anyway.