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 I looked at the source comparing both versions and I don't see any relevant changes in procps/pidof.c nor find_pid_by_name() of libbb/find_pid_by_name.c so I suspect the change is in procps_scan() (of libbb/procps.c) which is a little more complex. I'll continue sifting through the code to see if I can find the change, but figured it'd be worthwhile to ask those on here that are closer to the code that might happen to know. Interested to know if the change is intentional, or not so I can adapt our project (if needed). Many thanks for the great work on Busybox! --Marc _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
