This is the mail archive of the mailing list for the systemtap project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.4-189-ge04a4b4

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  e04a4b413bb5d66165acb459409d30c93660d990 (commit)
       via  8d1a21b3ef9153e345e0c9e66c24acc9596b3a2c (commit)
      from  ce4defd0134872508c9801ee666f9b1eb6a544b1 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit e04a4b413bb5d66165acb459409d30c93660d990
Author: Josh Stone <>
Date:   Mon Mar 21 20:01:39 2011 -0700

    Add a workaround for old systems without ppoll
    A coarse approximation of ppoll is added using sigprocmask and poll, as
    suggested in the ppoll manpage, but it doesn't carry the same atomic
    guarantee.  I've forced it to have a non-infinite polling timeout, so we
    won't block forever.
    NB: This only matters on the client connecting to a remote ssh host.
    * Check for the function ppoll.
    * configure, Regenerate.
    * remote.cxx (ppoll): Fill in for missing ppoll, with a healthy comment
      explaining why I think this implementation is Good Enoughâ?¢.

commit 8d1a21b3ef9153e345e0c9e66c24acc9596b3a2c
Author: Josh Stone <>
Date:   Mon Mar 21 15:30:32 2011 -0700

    remote: Try the legacy ssh code if stapsh isn't found
    The ssh remote command is restructured so that if stapsh isn't found in
    the remote PATH, it will exit 127 immediately.  On the local side, when
    we fail to read the stapsh uname response, we can check the exit status
    to know stapsh wasn't found.  Then we can try again with the old ssh
    code with a ControlMaster.  However, I'm limiting the fallback to only
    when there's a single remote, as signals and cleanup aren't really
    handled as well.  (That's the point of stapsh...)
    * remote.cxx (ssh_remote::create): New static function which tries a
      self-instantiation first, then if that fails to find stapsh, it tries
      again using ssh_legacy_remote instead.
      (ssh_remote::connect): Renamed from remote.  Now using a "type -P"
      trick to silently determine if stapsh is present, by exit code alone.
      (ssh_legacy_remote): Un-#ifdef'ed the old ssh_remote code, to get new
      life as our legacy access.
      (remote::create): Get ssh through ssh_remote::create.


Summary of changes:    |    3 +
 configure    |   78 +++++++++++++++++++++ |    1 +
 remote.cxx   |  214 +++++++++++++++++++++++++++++++++++-----------------------
 4 files changed, 212 insertions(+), 84 deletions(-)

systemtap: system-wide probe/trace tool

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]