public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.4-215-g0c38546 Date: Thu, 31 Mar 2011 16:23:00 -0000 [thread overview] Message-ID: <20110331162347.12604.qmail@sourceware.org> (raw) 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 0c385461d8cf7e6793b3f67411feae3c1ef5f1dc (commit) from f301a9ffc92637ab53ff5a1d29494c560cb7f37f (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 0c385461d8cf7e6793b3f67411feae3c1ef5f1dc Author: David Smith <dsmith@redhat.com> Date: Thu Mar 31 11:23:27 2011 -0500 Change the logger PMDA config file lines to be of the form "NAME PATHNAME". * pcp/src/pmdas/logger/logger.c (valid_pmns_name): New function. (read_config): Read NAME and PATHNAME from each config file line. Make sure NAME is a valid PMNS name. * pcp/src/pmdas/logger/Install: Ask for logfile names along with paths. * pcp/src/pmdas/logger/event.h: Swap the order of the logfile name and pathname to mirror the new config file. ----------------------------------------------------------------------- Summary of changes: pcp/src/pmdas/logger/Install | 29 ++++++--- pcp/src/pmdas/logger/event.h | 2 +- pcp/src/pmdas/logger/logger.c | 131 +++++++++++++++++++++++++++------------- 3 files changed, 108 insertions(+), 54 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-03-31 16:23 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20110331162347.12604.qmail@sourceware.org \ --to=dsmith@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).