Applied, thanks!

On Sun, Jan 8, 2017 at 9:24 AM, Kang-Che Sung <[email protected]> wrote:
> Fix ash "kill %1" not working if CONFIG_ASH is disabled but
> ash is launched by 'sh' or 'bash' name
>
> Signed-off-by: Kang-Che Sung <[email protected]>
> ---
>  procps/kill.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/procps/kill.c b/procps/kill.c
> index 57a33bcaa..198c78de0 100644
> --- a/procps/kill.c
> +++ b/procps/kill.c
> @@ -285,10 +285,10 @@ int kill_main(int argc UNUSED_PARAM, char **argv)
>
>   /* Looks like they want to do a kill. Do that */
>   while (arg) {
> -#if ENABLE_ASH || ENABLE_HUSH
> +#if ENABLE_ASH || ENABLE_SH_IS_ASH || ENABLE_BASH_IS_ASH
>   /*
>   * We need to support shell's "hack formats" of
> - * " -PRGP_ID" (yes, with a leading space)
> + * " -PGRP_ID" (yes, with a leading space)
>   * and " PID1 PID2 PID3" (with degenerate case "")
>   */
>   while (*arg != '\0') {
> --
> 2.11.0
> _______________________________________________
> busybox mailing list
> [email protected]
> http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to