Searched refs:reap (Results 1 – 17 of 17) sorted by relevance
28 reap=071 "r") reap=1;;203 if [ "${reap}" -gt 0 ]; then
17 - Process creation - number of times a process can fork and reap18 - Shell Scripts - number of times a process can start and reap a script
18 - Process creation - number of times a process can fork and reap19 - Shell Scripts - number of times a process can start and reap a script
20 Your backend must also provide an event handling function to "reap" ongoing37 platform, you can emulate this using an internal library thread to reap I/O as
456 self.reap(spec.shortname, spec.cpu_cost)465 def reap(self, waiting_for=None, waiting_for_cost=None): member in Jobset522 self.reap()
47 \fB\-\-reap\fP
2725 convert a test in test_capi to use unittest and reap threads.
3116 * run-native-test.sh: Do kill -9 and reap explicitly at end, since
2313 Handle EINTR returns from wait() correctly and reap
3927 自食其果 < reap\-what\-one\-has\-sown;5102 不勞而獲 < reap\-without\-sowing;20786 收割 < reap;22317 自食其果 > reap\-what\-one\-has\-sown;22466 不勞而獲 > reap\-without\-sowing;35254 收割 > reap;
1922 They that reap must sheaf and bind;
1213 May reap his conquest, and may least rejoice
3347 process has zombies it can reap. On the way out, if we reaped
6073 - Issue #17249: convert a test in test_capi to use unittest and reap threads.
135235 reap %35709 rip
161424 reap %26372 rip