07-21-2018
You said you want the MTBF for each node. The node 127.0.0.1 was always down (for all three times it appeared in the data in post #4 and for both times it appeared in the data in post #1).
If a node is never up, isn't the mean time between failures zero? What value were you expecting?
This User Gave Thanks to Don Cragun For This Post:
6 More Discussions You Might Find Interesting
1. Virtualization and Cloud Computing
Hear how the changing needs of massive scale-out computing is driving a transfomation in technology and learn how HP is supporting this new evolution of the web.
More... (1 Reply)
Discussion started by: Linux Bot
1 Replies
2. HP-UX
What are the server requirements, Software requirements, Network requirements etc,
Please help me.. as 'm new 'm unable to get things done @ my end alone.
Please refrain from typing subjects completely in upper case letters to get more attention, ty. (5 Replies)
Discussion started by: Sounddappan
5 Replies
3. Red Hat
Hi,
We are having many RedHat linux Server with Cluster facility for availability of service like HTTPD / MySQL.
We face some issue while some issue related to power disturbance / fluctuation or Network failure. There is two Cluster Node configured in... (0 Replies)
Discussion started by: hirenkmistry
0 Replies
4. What is on Your Mind?
Three days ago we received an expected notice from our long time data center that they were going dark on Sept 12th.
About one and a half hours ago, after three days of marathon work, I just cut over the unix.com to a new data center with a completely new OS and Ubuntu distribution. (22 Replies)
Discussion started by: Neo
22 Replies
5. What is on Your Mind?
Dear All,
There was a problem in the data center data, which caused the server to be unreachable for about an hour.
Server logs show the server did not crash or go down.
Hence, I assume there was a networking issue at the data center.
Still waiting for final word on what happened.
... (4 Replies)
Discussion started by: Neo
4 Replies
6. What is on Your Mind?
There was a problem with our data center today, creating a site outage (server unreachable).
That problem has been resolved.
Basically, it seems to have been a socially engineered denial-of-service attack against UNIX.com; which I stopped as soon as I found out what the problem was.
Total... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT DEBIAN
blt_treenodeid
Blt_TreeNodeId(3) BLT Library Procedures Blt_TreeNodeId(3)
__________________________________________________________________________________________________________________________________________________
NAME
Blt_TreeNodeId - Returns the node serial number.
SYNOPSIS
#include <bltTree.h>
unsigned int
Blt_TreeNodeId(node)
ARGUMENTS
Blt_TreeNode node (in) Node whose ID is to be returned.
_________________________________________________________________
DESCRIPTION
This procedure returns the node serial number. The node serial number is useful for programs that export the tree data object to the Tcl
programming level. Since node labels (and therefore pathnames) are not unique, the ID can be used to uniquely identify a node.
The arguments are as follows:
node The node whose serial number is returned. The serial number of the root node for example is always 0.
RETURNS
The serial number of the node. Nodes are given a unique serial number when they are created. You can use the ID to later retrieve the
node using Blt_TreeGetNode.
EXAMPLE
The following example prints the ID of a node.
printf("root ID is %s
", Blt_TreeNodeId(node));
KEYWORDS
Tcl_TreeCreateNode, Tcl_TreeDeleteNode
BLT
2.4 Blt_TreeNodeId(3)