[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[sysvinit-devel] Is pidof moving?

From: Craig Small
Subject: [sysvinit-devel] Is pidof moving?
Date: Wed, 11 Dec 2013 22:42:03 +1100
User-agent: Mutt/1.5.21 (2010-09-15)

Hi There,
  I'm writing this as the Debian procps packager.  I hope you can clear
something up for me. Please CC me as I'm not on the list.

I got some emails saying that pidof is moving from sysvinit-tools or
sysvinit-utils and needed a home, so I (as procps upstream) agreed that
it can have a home there.

When I discussed how this would work within Debian, there was some
confusion about it going at all?  I  couldn't see much in your email
list about this happening.

Is there two projects? One for RedHat and one for others?
Is pidof moving? Are there plans to remove killall5 which shares a lot
of its code as well?

If there are two projects and "your" project is keeping pidof but the
RedHat one is not, I can keep one pidof in upstream procps but as the
Debian maintainer keep that pidof out (and the sysvinit-tools packagers
will keep pidof there). It may be odd, but it would work.

Some answers would be great. I've held off doing anything with the
Debian procps package until I know what is going on.

 - Craig
Craig Small (@smallsees)       csmall at :
Debian GNU/Linux    csmall at :
GPG fingerprint:        5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

reply via email to

[Prev in Thread] Current Thread [Next in Thread]