Accept service unit name in mxstartups #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After 4ee8fed systems hang on shtudown until systemd times out. Do not wait for NIS on shutdown. Tell systemd to order nis and mxstartup in startup and shutdown
migrated from NIS to hostconfig
Restart not needed
Regard the 4th column of /etc/mxstartups as the name of a systemd service unit if it ends in ".service". In that case, ignore the username and use systemctl to start/stop that unit. The idea is to use /etc/mxstartups for services, which we want to run as a systems service, e.g. to use the features of systemd. Currently there is an option to use unit files with an encoded hostname but we prefer to have the information of which hosts starts which service in /etc/mxstartups.
|
oops. Wrong repository. |
Sign in
to join this conversation on GitHub.
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.
As discussed:
Regard the 4th column of /etc/mxstartups as the name of a systemd
service unit if it ends in ".service". In that case, ignore the
username and use systemctl to start/stop that unit.
The idea is to use /etc/mxstartups for services, which we want to run as
a systems service, e.g. to use the features of systemd. Currently there
is an option to use unit files with an encoded hostname but we prefer to
have the information of which hosts starts which service in
/etc/mxstartups.