Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring Event processing & machine learning in monitoring system Post 302821333 by DGPickett on Friday 14th of June 2013 11:44:01 AM
Old 06-14-2013
There is some of this sort of event predition in network protocols, to detect defective or slow paths to avoid, but servers are just supposed to run, not fail, predictable or not. The two flavors of handling this are parallel redundant concurrent load division where a dead server is detected and not sent any more load until it can respond to periodic tests. Recovery from services sent to a dying server is mostly left to client retry, but some systems of transactional middleware do requeue services that do not run to final commit, so they are run on alternative servers. Of course, query services are easier to handle than churn, where you need to rollback all when there is failure, before you requeue. Some systems do not use transactions, but structure churn so it can be applied any number of times and not have duplicate side effects (history filtering or believe the last of that seq. #).
 

We Also Found This Discussion For You

1. UNIX for Dummies Questions & Answers

learning UNIX on a Windows 2000 machine?

What is the best way to learn UNIX, shell, and Perl on a Windows 2000 machine? My place of employment uses Solaris and Perl and I would like to learn some UNIX skills on my home PC. I read about "dual boots", "Microsoft Windows Services for UNIX", and "cygwin". What other free options are... (9 Replies)
Discussion started by: wolfv
9 Replies
ypset(1M)																 ypset(1M)

NAME
ypset - bind to particular Network Information Service server SYNOPSIS
host] domain] server Remarks The Network Information Service (NIS) was formerly known as Yellow Pages (YP). Although the name has changed, the functionality of the service remains the same. DESCRIPTION
tells to get Network Information Service (NIS) services for the specified domain from the process running on server (see ypserv(1M) and ypbind(1M)). server is the NIS server that the NIS client binds to, and is specified as either a host name or an IP address. If server is down or is not running this is not discovered until a local NIS client process tries to obtain a binding for the domain. The daemon then tests the binding set by If the binding cannot be made to the requested server, attempts to rebind to another server in the same domain present in the ypservers file. NOTE: In order to run must be initiated with the or options. For more information on how to initiate see ypbind(1M). The command is useful for binding a client node that is not on a broadcast network. If a client node exists on a broadcast network which has no NIS server running, and if there is a network with one running that is available via a gateway, can establish a binding through that gateway. It is also useful for debugging NIS client applications such as when a NIS map exists only at a single NIS server. In cases where several hosts on the local net are supplying NIS services, it is possible for to rebind to another host, even while you attempt to find out if the operation succeeded. For example, typing followed by and receiving the reply may be confusing. It could occur when host1 does not respond to because its process is not running or is overloaded, and host2, running gets the binding. The server is the NIS server to bind to, specified as either a host name or an IP address. Refer to ypfiles(4) and ypserv(1M) for an overview of the Network Information Service. Options recognizes the following options and command-line arguments: Bind server for the Version 2 NIS protocol. Set the binding on host instead of locally. host can be specified as a host name or an IP address. Use domain instead of the default domain returned by (see domainname(1)). DIAGNOSTICS
The user is not root, or ypbind was run without the flags. See ypserv(1M) for explanations of the flags. The user is not root, or ypbind was run without one of the flags. See ypserv(1M) for explanations of the flags. WARNINGS
Starting with ONCplus version B.11.31.02, the NIS Version 1 protocol is no longer available. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
domainname(1), ypwhich(1), ypserv(1M), ypfiles(4). ypset(1M)
All times are GMT -4. The time now is 04:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy