Searched refs:signals (Results 1 – 15 of 15) sorted by relevance
| /busybox-1.35.0/libbb/ |
| D | u_signal_names.c | 33 static const char signals[][7] ALIGN1 = { variable
165 for (i = 0; i < ARRAY_SIZE(signals); i++) in get_signum()
166 if (strcasecmp(name, signals[i]) == 0) in get_signum()
236 if ((unsigned)number < ARRAY_SIZE(signals)) { in get_signame()
237 if (signals[number][0]) /* if it's not an empty str */ in get_signame()
238 return signals[number]; in get_signame()
251 for (signo = 1; signo < ARRAY_SIZE(signals); signo++) { in print_signames()
252 const char *name = signals[signo]; in print_signames()
|
| D | Kbuild.src | 88 lib-y += signals.o
|
| /busybox-1.35.0/init/ |
| D | halt.c | 172 static const smallint signals[] = { SIGUSR1, SIGUSR2, SIGTERM }; in halt_main() local
217 rc = kill(pidlist[0], signals[which]); in halt_main()
225 rc = kill(1, signals[which]); in halt_main()
227 rc = kill(1, signals[which]); in halt_main()
|
| /busybox-1.35.0/shell/hush_test/hush-signals/ |
| D | return_in_trap1.tests | 16 # and sets $?, then checks pending signals and runs a trap handler,
17 # or does it first check pending signals and runs handler?
|
| D | sigquit_exec.tests | 1 # Should show no masked signals in both cases.
|
| D | catch.tests | 1 # avoid ugly warnings about signals not being caught
|
| /busybox-1.35.0/shell/ash_test/ash-signals/ |
| D | return_in_trap1.tests | 16 # and sets $?, then checks pending signals and runs a trap handler,
17 # or does it first check pending signals and runs handler?
|
| D | sigquit_exec.tests | 1 # Should show no masked signals in both cases.
|
| D | catch.tests | 1 # avoid ugly warnings about signals not being caught
|
| /busybox-1.35.0/shell/ |
| D | README.job | 19 block all signals
20 unblock all signals
25 Process groups are used for distribution of signals, and by terminals
45 allow all signals
54 allow all signals
56 block all signals
57 allow all signals
59 allow all signals
61 block all signals
62 allow all signals
[all …]
|
| D | ash_doc.txt | 1 Wait + signals
|
| /busybox-1.35.0/docs/ |
| D | nofork_noexec.txt | 76 hush shell only handles signals (like ^C) after you return
98 Currently, ash shell signal handling is implemented in a way that signals
|
| /busybox-1.35.0/scripts/kconfig/ |
| D | qconf.h | 86 signals:
|
| /busybox-1.35.0/ |
| D | NOFORK_NOEXEC.lst | 377 time - spawner, longterm, changes state (signals)
378 timeout - spawner, longterm, changes state (signals)
|
| /busybox-1.35.0/examples/var_service/ |
| D | README | 159 This even works while fw service runs: if dhcp signals fw to (re)start
|