pcp
[Top] [All Lists]

pcp updates - Frank's pmmgr exec fix

To: pcp@xxxxxxxxxxx
Subject: pcp updates - Frank's pmmgr exec fix
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Tue, 08 Apr 2014 08:41:29 +1000
Delivered-to: pcp@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
Applied locally and tested.  All's well.

Thanks Frank.

Changes committed to git://oss.sgi.com/kenj/pcp.git dev

 src/pmmgr/pmmgr.cxx |    5 +++++
 1 file changed, 5 insertions(+)

commit 71e081e914dda7e172c45be84c872c1dc2331036
Merge: ea28d8f fcc4c3e
Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date:   Tue Apr 8 08:31:26 2014 +1000

    Merge branch 'fche/for-merge' of git://sourceware.org/git/pcpfans into dev

commit fcc4c3ee6f7c131e5327f234cde77adcb0721857
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date:   Mon Apr 7 13:00:10 2014 -0400

    pmmgr: use /bin/sh -c "exec FOO" instead of "FOO" for launching daemons
    
    It turns out that bash behaves differently from other shells when
    being invoked as "/bin/sh -c COMMAND".  For pmmgr's daemon-killing
    signals to work, the shell's pid must belong to the COMMAND (or at
    least, signals to $pid would need to be relayed).
    
    The easiest fix seems to be having pmmgr prefix "exec COMMAND" to
    force any shell's behavior into the bash default.

<Prev in Thread] Current Thread [Next in Thread>