Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing A load balancer for Nomachine NX Post 302964725 by MadeInGermany on Monday 18th of January 2016 01:14:20 PM
Old 01-18-2016
NX 3 had a dump round-robin dispatcher. If one of the NX nodes was rebooted, it was less loaded than the other nodes, and never caught up.
The nxpub simply adds a more sophisticated dispatcher, and is transparent i.e. there is no administrative change and no extra dependency.
If you are using another load balancer, then likely this one won't add any value.
 

5 More Discussions You Might Find Interesting

1. Programming

Load Balancer

Halo mates, I m going to write a load balancer with C. Does anybody know some good reference on this? Cheers, Elton (5 Replies)
Discussion started by: EltonSky
5 Replies

2. AIX

hacmp ip load balancer failover

Hi All, How do I failover on the ip load balancer (back and forth)? It involves first to load a new config on the passive ip. If success, load the new config on the ip active (which is now passive). Any idea, please. Thanks in advance. (0 Replies)
Discussion started by: itik
0 Replies

3. Red Hat

What is the Best Load Balancer for Linux?

Hi, What's the best load balancer for Linux (CentOS, SuSE) according to your personal experience? Linux Virtual Server (LVS) is a famous one, but their download site has not been updated since 2007. Their web and mailing list are so quiet. Is the Ultra Monkey project including LVS... (1 Reply)
Discussion started by: aixlover
1 Replies

4. UNIX for Advanced & Expert Users

piranha load balancer failover

we use piranha load balancer with two nodes even the primary node is running fine and up failover happend to secondary node this happend quite few times ehy node2 cannot talk to node1 what logs are to be checked and investigate why failover occured pulse: partner dead: activating... (0 Replies)
Discussion started by: robo
0 Replies

5. Linux

Server Load balancer

Hello Guys, Hope you all doing well . :) I was checking load balance command (uptime)on VM server and got below output. # uptime 07:08:40 up 52 min, 2 users,a load average: 0.45, 0.11, 0.03 A :How we can calculate load average? Thank you in advance !! Cheers:) Dont forget... (1 Reply)
Discussion started by: Nats
1 Replies
AUDISPD:(8)						  System Administration Utilities					       AUDISPD:(8)

NAME
audispd - an event multiplexor SYNOPSIS
audispd DESCRIPTION
audispd is an audit event multiplexor. It has to be started by the audit daemon in order to get events. It takes audit events and distrib- utes them to child programs that want to analyze events in realtime. When the audit daemon recieves a SIGTERM or SIGHUP, it passes that signal to the dispatcher, too. The dispatcher in turn passes those signals to its child processes. The child programs install a configuration file in a plugins directory, /etc/audisp/plugins.d. Filenames are not allowed to have more than one '.' in the name or it will be treated as a backup copy and skipped. Options are given one per line with an equal sign between the key- word and its value. The available options are as follows: active The options for this are yes or no. direction The option is dictated by the plugin. In or out are the only choices. You cannot make a plugin operate in a way it wasn't designed just by changing this option.This option is to give a clue to the event dispatcher about which direction events flow. NOTE: inbound events are not supported yet. path This is the absolute path to the plugin executable. In the case of internal plugins, it would be the name of the plugin. type This tells the dispatcher how the plugin wants to be run. Choices are builtin and always. Builtin should always be given for plug- ins that are internal to the audit event dispatcher. These are af_unix and syslog. The option always should be given for most if not all plugins. The default setting is always. args This allows you to pass arguments to the child program. Generally plugins do not take arguments and have their own config file that instructs them how they should be configured. At the moment, there is a limit of 2 args. format The valid options for this are binary and string. Binary passes the data exactly as the audit event dispatcher gets it from the audit daemon. The string option tells the dispatcher to completely change the event into a string suitable for parsing with the audit parsing library. The default value is string. FILES
/etc/audisp/audispd.conf /etc/audisp/plugins.d SEE ALSO
audispd.conf(5), auditd(8). AUTHOR
Steve Grubb Red Hat Sept 2007 AUDISPD:(8)
All times are GMT -4. The time now is 03:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy