Bug 9661 - udhcpc is unable to handle signals
Summary: udhcpc is unable to handle signals
Status: RESOLVED WORKSFORME
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.23.x
Hardware: Other Linux
: P3 major
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-17 10:03 UTC by shrinivas
Modified: 2017-02-17 18:21 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description shrinivas 2017-02-17 10:03:35 UTC 
The signal handling of SIGUSR1 and SIGUSR2 for connection renew and release appears to be broken with this release. This was working in release 1.19.x
Comment 1 shrinivas 2017-02-17 10:04:52 UTC 
udhcpc --help also doesnt give any information about signals
Comment 2 Denys Vlasenko 2017-02-17 17:50:16 UTC 
(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
Comment 3 Denys Vlasenko 2017-02-17 18:21:16 UTC 
Tested current git: SIGUSR1/2 work