From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents-4.0.8 stable release
Date: Mon, 07 Apr 2014 14:39:22 +0200 [thread overview]
Message-ID: <53429C7A.9050905@redhat.com> (raw)
Welcome to the fence-agents 4.0.8 release.
This release includes new fence agent for Raritan and several bugfixes:
* fence_wti respects delay option in telnet connections
* fixed problem when using identity file for login via ssh
* correct values in manual pages for symlinks
* allow SSl connection to fallback to SSL 3.0 (--notls) used for HP iLO2
The new source tarball can be downloaded here:
https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-4.0.8.tar.xz
To report bugs or issues:
https://bugzilla.redhat.com/
Would you like to meet the cluster team or members of its community?
Join us on IRC (irc.freenode.net #linux-cluster) and share your
experience with other sysadministrators or power users.
Thanks/congratulations to all people that contributed to achieve this
great milestone.
m,
reply other threads:[~2014-04-07 12:39 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=53429C7A.9050905@redhat.com \
--to=mgrac@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: link
Be 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 NNTP newsgroup(s).