You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A container represents a set of child processes (or threads) which are doing work for you.
30
18
31
-
```ruby
19
+
```ruby
32
20
require'async/container'
33
21
34
22
Async.logger.debug!
@@ -50,7 +38,7 @@ Async.logger.debug "Finished."
50
38
51
39
The controller provides the life-cycle management for one or more containers of processes. It provides behaviour like starting, restarting, reloading and stopping. You can see some [example implementations in Falcon](https://github.com/socketry/falcon/blob/master/lib/falcon/controller/). If the process running the controller receives `SIGHUP` it will recreate the container gracefully.
52
40
53
-
```ruby
41
+
```ruby
54
42
require'async/container'
55
43
56
44
Async.logger.debug!
@@ -77,7 +65,7 @@ controller.run
77
65
78
66
`SIGINT` is the interrupt signal. The terminal sends it to the foreground process when the user presses **ctrl-c**. The default behavior is to terminate the process, but it can be caught or ignored. The intention is to provide a mechanism for an orderly, graceful shutdown.
79
67
80
-
`SIGQUIT` is the dump core signal. The terminal sends it to the foreground process when the user presses **ctrl-\**. The default behavior is to terminate the process and dump core, but it can be caught or ignored. The intention is to provide a mechanism for the user to abort the process. You can look at `SIGINT` as "user-initiated happy termination" and `SIGQUIT` as "user-initiated unhappy termination."
68
+
`SIGQUIT` is the dump core signal. The terminal sends it to the foreground process when the user presses **ctrl-\\**. The default behavior is to terminate the process and dump core, but it can be caught or ignored. The intention is to provide a mechanism for the user to abort the process. You can look at `SIGINT` as "user-initiated happy termination" and `SIGQUIT` as "user-initiated unhappy termination."
81
69
82
70
`SIGTERM` is the termination signal. The default behavior is to terminate the process, but it also can be caught or ignored. The intention is to kill the process, gracefully or not, but to first allow it a chance to cleanup.
83
71
@@ -109,11 +97,11 @@ WantedBy=multi-user.target
109
97
110
98
## Contributing
111
99
112
-
1. Fork it
113
-
2. Create your feature branch (`git checkout -b my-new-feature`)
114
-
3. Commit your changes (`git commit -am 'Add some feature'`)
115
-
4. Push to the branch (`git push origin my-new-feature`)
116
-
5. Create new Pull Request
100
+
1.Fork it
101
+
2.Create your feature branch (`git checkout -b my-new-feature`)
102
+
3.Commit your changes (`git commit -am 'Add some feature'`)
103
+
4.Push to the branch (`git push origin my-new-feature`)
0 commit comments