[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Using 'pidof' with Absolute Path to Process
From:       Marc Smith <msmith626 () gmail ! com>
Date:       2019-06-16 2:37:45
Message-ID: CAH6h+he1hzwqW0vE-ki7URk3E_KBJ6XPOWdairKG0va_UPu+Ow () mail ! gmail ! com
[Download RAW message or body]

Awesome, thanks!

On Sat, Jun 15, 2019 at 12:38 PM Denys Vlasenko
<vda.linux@googlemail.com> wrote:
>
> On Tue, Jun 11, 2019 at 8:07 PM Marc Smith <msmith626@gmail.com> wrote:
> > Hi,
> >
> > We previously used Busybox 1.26.2 in our project and just recently
> > upgraded to Busybox 1.30.1. I noticed a change in the 'pidof'
> > behavior... previously we could give the absolute path of a running
> > program to 'pidof' and it would work properly (exit 0 and return PID's
> > of matching processes). But with 1.30.1 it seems to no longer work
> > this way:
> > [root@node-1 ~]# ps ax | grep corosync
> >  1648 root      0:51 /usr/sbin/corosync
> >
> > [root@node-1 ~]# pidof corosync
> > 1648
> > [root@node-1 ~]# echo $?
> > 0
> >
> > [root@node-1 ~]# pidof /usr/sbin/corosync
> > [root@node-1 ~]# echo $?
> > 1
>
>
> Fixed in git.
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]