public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: fabbione@sourceware.org To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com Subject: Cluster Project branch, STABLE2, updated. cluster-2.03.04-13-ga2c34ee Date: Mon, 16 Jun 2008 11:07:00 -0000 [thread overview] Message-ID: <20080616110706.11354.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 "Cluster Project". http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=a2c34ee98442ba23aac8dd3fe6d19b22f3d65b6d The branch, STABLE2 has been updated via a2c34ee98442ba23aac8dd3fe6d19b22f3d65b6d (commit) from 72e56df08d77b3ff2bea852dcf66ce7b3eb6171e (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 a2c34ee98442ba23aac8dd3fe6d19b22f3d65b6d Author: James Parsons <jparsons@redhat.com> Date: Wed Aug 8 15:49:57 2007 +0000 Fix for 251358 ----------------------------------------------------------------------- Summary of changes: fence/agents/egenera/fence_egenera.pl | 22 +++++++++++++++++++++- 1 files changed, 21 insertions(+), 1 deletions(-) diff --git a/fence/agents/egenera/fence_egenera.pl b/fence/agents/egenera/fence_egenera.pl index 245243e..6970a13 100644 --- a/fence/agents/egenera/fence_egenera.pl +++ b/fence/agents/egenera/fence_egenera.pl @@ -14,6 +14,7 @@ $BUILD_DATE=""; # Get the program name from $0 and strip directory names $_=$0; +$|=1; s/.*\///; my $pname = $_; @@ -150,6 +151,10 @@ sub get_options_stdin # FIXME should we do more error checking? # Excess name/vals will be eaten for now + else + { + fail "parse error: unknown option \"$opt\""; + } } } @@ -256,7 +261,7 @@ sub pserver_boot } # Is there any harm in sending this command multiple times? - my $cmd = "ssh $cserv $esh blade -b $_"; + my $cmd = "ssh $cserv $esh pserver -b $lpan/$pserv"; my $pid = open3 (\*WTR, \*RDR,\*RDR, $cmd) or die "error open3(): $!"; @@ -278,11 +283,15 @@ sub pserver_boot sub pserver_shutdown { my $rtrn=1; + local *egen_log; + open(egen_log,">/tmp/eglog"); for (my $trys=0; $trys<20; $trys++) { last if (pserver_status != 0); + my $status = $_; + print egen_log "shutdown: $trys $status\n"; if (/^Shutdown/) { $rtrn=0; @@ -294,6 +303,12 @@ sub pserver_shutdown # do I need to do anything here? # We'll just wait for now } + elsif (/^Booted\(KDB\)/ || /^Debugging/ ) + { + print egen_log "shutdown: crash dump being performed. Waiting\n"; + $rtrn=0; + last; + } else { if (pserver_pblade) @@ -304,8 +319,12 @@ sub pserver_shutdown # is there any harm in sending this command multiple # times? my $cmd = "ssh $cserv $esh blade -s $_"; + print egen_log "shutdown: $cmd being called, before open3\n"; my $pid = open3 (\*WTR, \*RDR,\*RDR, $cmd) or die "error open3(): $!"; + print egen_log "shutdown: after calling open3\n"; + @outlines = <RDR>; + print egen_log "shutdown: Open3 result: ", @outlines, "\n"; close WTR; close RDR; @@ -316,6 +335,7 @@ sub pserver_shutdown sleep 1; } + print egen_log "shutdown: Returning from pserver_shutdown with return code $rtrn\n"; return $rtrn; } hooks/post-receive -- Cluster Project
reply other threads:[~2008-06-16 11:07 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=20080616110706.11354.qmail@sourceware.org \ --to=fabbione@sourceware.org \ --cc=cluster-cvs@sources.redhat.com \ --cc=cluster-devel@redhat.com \ /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).