Allow non-standard max length for a service name #96
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.
This is to solve issue #94 .
A new method
ServiceDaemon.set_service_name_len_max()
is added to support setting a custom max length for the service name.A public constant
SERVICE_NAME_LEN_MAX_DEFAULT
is defined for the default / standard value.Service name length error reporting (a trade-off): it will no longer return Error directly from
register()
method for service name length errors. Instead, it will be reported in error log andDaemonEvent::Error
received by any monitors. The register itself will not succeed in such error cases. See the test case changes for an example.