| Summary: | udhcpc is unable to handle signals | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | shrinivas <kerneldeveloper28> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | busybox-cvs |
| Priority: | P3 | ||
| Version: | 1.23.x | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
shrinivas
2017-02-17 10:03:35 UTC
udhcpc --help also doesnt give any information about signals (In reply to shrinivas from comment #1) > udhcpc --help also doesnt give any information about signals In 1.26.2, it does: $ busybox | grep 'BusyBox v' BusyBox v1.26.2 (2017-01-16 16:47:56 CET) multi-call binary. $ busybox udhcpc --help BusyBox v1.26.2 (2017-01-16 16:47:56 CET) multi-call binary. Usage: udhcpc [-fbqRB] [-a[MSEC]] [-t N] [-T SEC] [-A SEC/-n] [-i IFACE] [-P PORT] [-s PROG] [-p PIDFILE] [-oC] [-r IP] [-V VENDOR] [-F NAME] [-x OPT:VAL]... [-O OPT]... -i,--interface IFACE Interface to use (default eth0) ... -C,--clientid-none Don't send MAC as client identifier Signals: USR1 Renew lease USR2 Release lease ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ HERE Tested current git: SIGUSR1/2 work |