The Experts below are selected from a list of 114657 Experts worldwide ranked by ideXlab platform
Brad Nichols - One of the best experts on this subject based on the ideXlab platform.
-
tru64 unix cluster hooks file System Hierarchy cdsl pid
2003Co-Authors: Scott Fafrak, Jim Lola, Dennis Obrien, Greg Yates, Brad NicholsAbstract:UNIX operating System enables a more seamless transition from a standalone System to a cluster. Once a System joins or forms a cluster, it becomes a member of the cluster. Tru64 UNIX version 5.0, the /etc/rc.config file has been split into two files. rc.config and rc. config, common. A CDSL is a symbolic link with the “{memb}” variable as part of the path. The “{memb}” is the “context”, or more appropriately, what is resolved to determine what the context. Configuring a network interface is a member-specific task. The rcmgr command is the recommended method for modifying the rc.config files on Tru64 UNIX. The file System Hierarchy in Tru64 UNIX version 5 has been modified slightly from the version 4 layout. CDSL is a “behind-the-scenes” feature to make the life as an administrator easier. CDSL should be managed in a perfect way. Since a CDSL is a symbolic link, command can be used with the “s” option, although, it is highly recommended to use the mkcdsl command. The mkcdsl command is designed not to create just a CDSL, but to create a CDSL that can be maintained. Process Identities (PID) have been expanded to a 32-bit integer beginning in Tru64 UNIX version 5. In a stand-alone environment, there is no appreciable difference; for instance, PID 0 is still [kernel idle] and PID 1 is still the init daemon. The PID structure in a TruCluster environment, however, is defined to provide a unique range of process IDs (524288 PIDs/member).
-
Tru64 UNIX Cluster Hooks: File System Hierarchy, CDSL, & PID
TruCluster Server Handbook, 2003Co-Authors: Scott Fafrak, Jim Lola, Greg Yates, Dennis O'brien, Brad NicholsAbstract:UNIX operating System enables a more seamless transition from a standalone System to a cluster. Once a System joins or forms a cluster, it becomes a member of the cluster. Tru64 UNIX version 5.0, the /etc/rc.config file has been split into two files. rc.config and rc. config, common. A CDSL is a symbolic link with the “{memb}” variable as part of the path. The “{memb}” is the “context”, or more appropriately, what is resolved to determine what the context. Configuring a network interface is a member-specific task. The rcmgr command is the recommended method for modifying the rc.config files on Tru64 UNIX. The file System Hierarchy in Tru64 UNIX version 5 has been modified slightly from the version 4 layout. CDSL is a “behind-the-scenes” feature to make the life as an administrator easier. CDSL should be managed in a perfect way. Since a CDSL is a symbolic link, command can be used with the “s” option, although, it is highly recommended to use the mkcdsl command. The mkcdsl command is designed not to create just a CDSL, but to create a CDSL that can be maintained. Process Identities (PID) have been expanded to a 32-bit integer beginning in Tru64 UNIX version 5. In a stand-alone environment, there is no appreciable difference; for instance, PID 0 is still [kernel idle] and PID 1 is still the init daemon. The PID structure in a TruCluster environment, however, is defined to provide a unique range of process IDs (524288 PIDs/member).
-
6 tru64 unix cluster hooks file System Hierarchy cdsl pid
TruCluster Server Handbook, 2003Co-Authors: Scott Fafrak, Jim Lola, Dennis Obrien, Greg Yates, Brad NicholsAbstract:Publisher Summary UNIX operating System enables a more seamless transition from a standalone System to a cluster. Once a System joins or forms a cluster, it becomes a member of the cluster. Tru64 UNIX version 5.0, the /etc/rc.config file has been split into two files. rc.config and rc. config, common. A CDSL is a symbolic link with the “{memb}” variable as part of the path. The “{memb}” is the “context”, or more appropriately, what is resolved to determine what the context. Configuring a network interface is a member-specific task. The rcmgr command is the recommended method for modifying the rc.config files on Tru64 UNIX. The file System Hierarchy in Tru64 UNIX version 5 has been modified slightly from the version 4 layout. CDSL is a “behind-the-scenes” feature to make the life as an administrator easier. CDSL should be managed in a perfect way. Since a CDSL is a symbolic link, command can be used with the “s” option, although, it is highly recommended to use the mkcdsl command. The mkcdsl command is designed not to create just a CDSL, but to create a CDSL that can be maintained. Process Identities (PID) have been expanded to a 32-bit integer beginning in Tru64 UNIX version 5. In a stand-alone environment, there is no appreciable difference; for instance, PID 0 is still [kernel idle] and PID 1 is still the init daemon. The PID structure in a TruCluster environment, however, is defined to provide a unique range of process IDs (524288 PIDs/member).
Eric Horvitz - One of the best experts on this subject based on the ideXlab platform.
-
Exploiting System Hierarchy to Compute Repair Plans in Probabilistic Model-based Diagnosis
arXiv: Artificial Intelligence, 2013Co-Authors: Sampath Srinivas, Eric HorvitzAbstract:The goal of model-based diagnosis is to isolate causes of anomalous System behavior and recommend inexpensive repair actions in response. In general, precomputing optimal repair policies is intractable. To date, investigators addressing this problem have explored approximations that either impose restrictions on the System model (such as a single fault assumption) or compute an immediate best action with limited lookahead. In this paper, we develop a formulation of repair in model-based diagnosis and a repair algorithm that computes optimal sequences of actions. This optimal approach is costly but can be applied to precompute an optimal repair strategy for compact Systems. We show how we can exploit a hierarchical System specification to make this approach tractable for large Systems. When introducing Hierarchy, we also consider the tradeoff between simply replacing a component and decomposing it to repair its subcomponents. The hierarchical repair algorithm is suitable for off-line precomputation of an optimal repair strategy. A modification of the algorithm takes advantage of an iterative deepening scheme to trade off inference time and the quality of the computed strategy.
-
UAI - Exploiting System Hierarchy to compute repair plans in probabilistic model-based diagnosis
1995Co-Authors: Sampath Srinivas, Eric HorvitzAbstract:The goal of model-based diagnosis is to isolate causes of anomalous System behavior and recommend cost-effective repair actions. In general, precomputing optimal repair policies is intractable. To date, investigators addressing this problem have explored approximations that either impose restrictions on the System model, such as a single fault assumption, or that compute an immediate best action with limited lookahead. In this paper, we develop a formulation of repair in model-based diagnosis and a repair algorithm that computes optimal sequences of actions. This optimal approach is costly but can be applied to precompute an optimal repair strategy for compact Systems. We show how we can exploit a hierarchical System specification to make this approach tractable for large Systems. When introducing Hierarchy, we also consider the tradeoff between simply replacing a component and decomposing it to repair its subcomponents. The hierarchical repair algorithm is suitable for off-line precomputation of an optimal repair strategy. A modification of the algorithm takes advantage of an iterative deepening scheme to trade off inference time and the quality of the computed strategy.
Scott Fafrak - One of the best experts on this subject based on the ideXlab platform.
-
tru64 unix cluster hooks file System Hierarchy cdsl pid
2003Co-Authors: Scott Fafrak, Jim Lola, Dennis Obrien, Greg Yates, Brad NicholsAbstract:UNIX operating System enables a more seamless transition from a standalone System to a cluster. Once a System joins or forms a cluster, it becomes a member of the cluster. Tru64 UNIX version 5.0, the /etc/rc.config file has been split into two files. rc.config and rc. config, common. A CDSL is a symbolic link with the “{memb}” variable as part of the path. The “{memb}” is the “context”, or more appropriately, what is resolved to determine what the context. Configuring a network interface is a member-specific task. The rcmgr command is the recommended method for modifying the rc.config files on Tru64 UNIX. The file System Hierarchy in Tru64 UNIX version 5 has been modified slightly from the version 4 layout. CDSL is a “behind-the-scenes” feature to make the life as an administrator easier. CDSL should be managed in a perfect way. Since a CDSL is a symbolic link, command can be used with the “s” option, although, it is highly recommended to use the mkcdsl command. The mkcdsl command is designed not to create just a CDSL, but to create a CDSL that can be maintained. Process Identities (PID) have been expanded to a 32-bit integer beginning in Tru64 UNIX version 5. In a stand-alone environment, there is no appreciable difference; for instance, PID 0 is still [kernel idle] and PID 1 is still the init daemon. The PID structure in a TruCluster environment, however, is defined to provide a unique range of process IDs (524288 PIDs/member).
-
Tru64 UNIX Cluster Hooks: File System Hierarchy, CDSL, & PID
TruCluster Server Handbook, 2003Co-Authors: Scott Fafrak, Jim Lola, Greg Yates, Dennis O'brien, Brad NicholsAbstract:UNIX operating System enables a more seamless transition from a standalone System to a cluster. Once a System joins or forms a cluster, it becomes a member of the cluster. Tru64 UNIX version 5.0, the /etc/rc.config file has been split into two files. rc.config and rc. config, common. A CDSL is a symbolic link with the “{memb}” variable as part of the path. The “{memb}” is the “context”, or more appropriately, what is resolved to determine what the context. Configuring a network interface is a member-specific task. The rcmgr command is the recommended method for modifying the rc.config files on Tru64 UNIX. The file System Hierarchy in Tru64 UNIX version 5 has been modified slightly from the version 4 layout. CDSL is a “behind-the-scenes” feature to make the life as an administrator easier. CDSL should be managed in a perfect way. Since a CDSL is a symbolic link, command can be used with the “s” option, although, it is highly recommended to use the mkcdsl command. The mkcdsl command is designed not to create just a CDSL, but to create a CDSL that can be maintained. Process Identities (PID) have been expanded to a 32-bit integer beginning in Tru64 UNIX version 5. In a stand-alone environment, there is no appreciable difference; for instance, PID 0 is still [kernel idle] and PID 1 is still the init daemon. The PID structure in a TruCluster environment, however, is defined to provide a unique range of process IDs (524288 PIDs/member).
-
6 tru64 unix cluster hooks file System Hierarchy cdsl pid
TruCluster Server Handbook, 2003Co-Authors: Scott Fafrak, Jim Lola, Dennis Obrien, Greg Yates, Brad NicholsAbstract:Publisher Summary UNIX operating System enables a more seamless transition from a standalone System to a cluster. Once a System joins or forms a cluster, it becomes a member of the cluster. Tru64 UNIX version 5.0, the /etc/rc.config file has been split into two files. rc.config and rc. config, common. A CDSL is a symbolic link with the “{memb}” variable as part of the path. The “{memb}” is the “context”, or more appropriately, what is resolved to determine what the context. Configuring a network interface is a member-specific task. The rcmgr command is the recommended method for modifying the rc.config files on Tru64 UNIX. The file System Hierarchy in Tru64 UNIX version 5 has been modified slightly from the version 4 layout. CDSL is a “behind-the-scenes” feature to make the life as an administrator easier. CDSL should be managed in a perfect way. Since a CDSL is a symbolic link, command can be used with the “s” option, although, it is highly recommended to use the mkcdsl command. The mkcdsl command is designed not to create just a CDSL, but to create a CDSL that can be maintained. Process Identities (PID) have been expanded to a 32-bit integer beginning in Tru64 UNIX version 5. In a stand-alone environment, there is no appreciable difference; for instance, PID 0 is still [kernel idle] and PID 1 is still the init daemon. The PID structure in a TruCluster environment, however, is defined to provide a unique range of process IDs (524288 PIDs/member).
Arunava Roy - One of the best experts on this subject based on the ideXlab platform.
-
a structure based software reliability allocation using fuzzy analytic Hierarchy process
International Journal of Systems Science, 2015Co-Authors: S Chatterjee, J B Singh, Arunava RoyAbstract:During the design phase of a software, it is often required to evaluate the reliability of the software System. At this stage of development, one crucial question arises ‘how to achieve a target reliability of the software?’ Reliability allocation methods can be used to set reliability goals for individual components. In this paper, a software reliability allocation model has been proposed incorporating the user view point about various functions of a software. Proposed reliability allocation method attempts to answer the question ‘how reliable should the System components be?' The proposed model will be useful for determining the reliability goal at the planning and design phase of a software project, hence making reliability a singular measure for performance evaluation. Proposed model requires a Systematic formulation of user requirements and preference into the technical design and reliability of the software. To accomplish this task, a System Hierarchy has been established, which combines the user’s ...
Sampath Srinivas - One of the best experts on this subject based on the ideXlab platform.
-
Exploiting System Hierarchy to Compute Repair Plans in Probabilistic Model-based Diagnosis
arXiv: Artificial Intelligence, 2013Co-Authors: Sampath Srinivas, Eric HorvitzAbstract:The goal of model-based diagnosis is to isolate causes of anomalous System behavior and recommend inexpensive repair actions in response. In general, precomputing optimal repair policies is intractable. To date, investigators addressing this problem have explored approximations that either impose restrictions on the System model (such as a single fault assumption) or compute an immediate best action with limited lookahead. In this paper, we develop a formulation of repair in model-based diagnosis and a repair algorithm that computes optimal sequences of actions. This optimal approach is costly but can be applied to precompute an optimal repair strategy for compact Systems. We show how we can exploit a hierarchical System specification to make this approach tractable for large Systems. When introducing Hierarchy, we also consider the tradeoff between simply replacing a component and decomposing it to repair its subcomponents. The hierarchical repair algorithm is suitable for off-line precomputation of an optimal repair strategy. A modification of the algorithm takes advantage of an iterative deepening scheme to trade off inference time and the quality of the computed strategy.
-
UAI - Exploiting System Hierarchy to compute repair plans in probabilistic model-based diagnosis
1995Co-Authors: Sampath Srinivas, Eric HorvitzAbstract:The goal of model-based diagnosis is to isolate causes of anomalous System behavior and recommend cost-effective repair actions. In general, precomputing optimal repair policies is intractable. To date, investigators addressing this problem have explored approximations that either impose restrictions on the System model, such as a single fault assumption, or that compute an immediate best action with limited lookahead. In this paper, we develop a formulation of repair in model-based diagnosis and a repair algorithm that computes optimal sequences of actions. This optimal approach is costly but can be applied to precompute an optimal repair strategy for compact Systems. We show how we can exploit a hierarchical System specification to make this approach tractable for large Systems. When introducing Hierarchy, we also consider the tradeoff between simply replacing a component and decomposing it to repair its subcomponents. The hierarchical repair algorithm is suitable for off-line precomputation of an optimal repair strategy. A modification of the algorithm takes advantage of an iterative deepening scheme to trade off inference time and the quality of the computed strategy.
