Services declared as oneshot are expected to take some action and exit immediatelly (thus, they are not really services,
no running processes remain). A common pattern for these type of service is to be defined by a setup and a teardown action.
Let's create a example foo service that when started creates a file, and when stopped it deletes it.
Create executable file /opt/foo/setup-foo.sh:
| Code | Message | Description |
|---|---|---|
| 100 | Continue | The server has received the request headers, and the client should proceed to send the request body |
| 101 | Switching Protocols | The requester has asked the server to switch protocols |
| 103 | Checkpoint | Used in the resumable requests proposal to resume aborted PUT or POST requests |
| Code | Message | Description |
|---|
| # github.com/rafi i3status config | |
| # i3status configuration file | |
| # see "man i3status" for documentation. | |
| # It is important that this file is edited as UTF-8. | |
| # The following line should contain a sharp s: | |
| # ß | |
| # If the above line is not correctly displayed, fix your editor first! |