monitor server connections
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 6261
Virtual server monitor 0.5
Virtual server monitor (vsmon) is a monitoring tool for Linux-VServer. more>>
Virtual server monitor (vsmon) is a monitoring tool for Linux-VServer that gives a system administrator a global view of all vservers running on his park.
For now, it does not offer control over the vservers life cycle (e.g. provisioning, start, stop, and restart operations). To use vsmon, you must deploy one backend on each vserver host and one frontend, preferably in its own vserver.
Enhancements:
- The frontend was reworked to display a summary of all hosts.
- An owner can be assigned to each vserver.
- The backend can be used on hosts without Linux-VServers, and it no longer obtains IP addresses.
- The libdnet dependency was removed.
- The parsing of /proc/"pid"/stat now works for kernel 2.6.18.
- A Nagios plugin was added, which enables the use of the vsmon backend to monitor a host disk, memory, and swap.
- The plugin monitors all mount points according to an "intelligent" algorithm, which determines warning and critical thresolds as a function of the total size of the partition.
<<lessFor now, it does not offer control over the vservers life cycle (e.g. provisioning, start, stop, and restart operations). To use vsmon, you must deploy one backend on each vserver host and one frontend, preferably in its own vserver.
Enhancements:
- The frontend was reworked to display a summary of all hosts.
- An owner can be assigned to each vserver.
- The backend can be used on hosts without Linux-VServers, and it no longer obtains IP addresses.
- The libdnet dependency was removed.
- The parsing of /proc/"pid"/stat now works for kernel 2.6.18.
- A Nagios plugin was added, which enables the use of the vsmon backend to monitor a host disk, memory, and swap.
- The plugin monitors all mount points according to an "intelligent" algorithm, which determines warning and critical thresolds as a function of the total size of the partition.
Download (MB)
Added: 2007-01-16 License: GPL (GNU General Public License) Price:
1015 downloads
Aranha server monitor 0.1.0
Aranha server monitor is an application using rrdtool and XML-RPC to monitor servers with a XUL GUI. more>>
Aranha is an application that uses an XML-RPC layer to retrieve information from one or more servers. The type of information gathered is implemented via plugins, and can be displayed or archived in several different ways.
The data is gathered in Round Robin Databases (integrated with rrdtool) and can be accessed using a XUL interface available from the system. Plugins are very easy to write.
Configuration
To configure this module, either pass specific configuration values to
Makefile.PL like this:
perl Makefile.PL CONFIG_VAR="config val"
or
edit the %DEFAULTS variable on the toplevel Makefile.PL
Installation
To install this module type the following:
perl Makefile.PL
make
make test
make install
<<lessThe data is gathered in Round Robin Databases (integrated with rrdtool) and can be accessed using a XUL interface available from the system. Plugins are very easy to write.
Configuration
To configure this module, either pass specific configuration values to
Makefile.PL like this:
perl Makefile.PL CONFIG_VAR="config val"
or
edit the %DEFAULTS variable on the toplevel Makefile.PL
Installation
To install this module type the following:
perl Makefile.PL
make
make test
make install
Download (0.080MB)
Added: 2005-04-12 License: GPL (GNU General Public License) Price:
1656 downloads
Jabber::Connection 0.03
Jabber::Connection is a simple Perl module with connectivity functions for Jabber. more>>
SYNOPSIS
# client connection:
my $c = new Jabber::Connection(
server => jabber.org,
log => 1,
);
# component connection:
# my $c = new Jabber::Connection(
# server => localhost:5700,
# localname => comp.localhost,
# ns => jabber:component:accept,
# log => 1,
# debug => 1,
# );
die "oops: ".$c->lastError unless $c->connect();
$c->register_beat(10, &every_10_seconds);
$c->register_handler(presence,&presence);
$c->register_handler(iq,&handle_iq_conference);
$c->register_handler(iq,&handle_iq_browse);
$c->auth(qmacro,password,myresource); # client auth
# $c->auth(secret); # component auth
$c->send( );
$c->start;
DESCRIPTION ^
The Jabber::Connection package provides basic functions for connecting clients and components to a Jabber server.
Download (0.012MB)
Added: 2007-03-21 License: Perl Artistic License Price:
952 downloads
NWN Server Administration 0.9.8
NWN Server Administration is a Web interface for managing NeverWinter Night servers. more>>
NWN Server Administration is a Web interface for managing NeverWinter Night servers.
This interface provides many features for monitoring and controlling multiple servers on the same computer.
The interface provides support for nwnx, and has an interface for running database queries.
Enhancements:
- Fixed problem with Character Administration with usernames with symbols in their names such as -. Also fixed
- the Administration privileges with same problem.
- Fixed issue with a Non-Privileged user couldnt download the NWN Campaigns.
- Fixed issue with deleting a character with a symbol in the name.
- Added HotU portraits and classes.
- Changed access privileges on Character Administration. Made Deleting characters a separate privileges.
- Changed access on Uploading files, Upload is now a separate privilege.
- Added a NWN Server Administration Options page, currently has adminemail address setting, and ability to hide/show unprivileged commands to the user.
<<lessThis interface provides many features for monitoring and controlling multiple servers on the same computer.
The interface provides support for nwnx, and has an interface for running database queries.
Enhancements:
- Fixed problem with Character Administration with usernames with symbols in their names such as -. Also fixed
- the Administration privileges with same problem.
- Fixed issue with a Non-Privileged user couldnt download the NWN Campaigns.
- Fixed issue with deleting a character with a symbol in the name.
- Added HotU portraits and classes.
- Changed access privileges on Character Administration. Made Deleting characters a separate privileges.
- Changed access on Uploading files, Upload is now a separate privilege.
- Added a NWN Server Administration Options page, currently has adminemail address setting, and ability to hide/show unprivileged commands to the user.
Download (1.3MB)
Added: 2005-11-02 License: GPL (GNU General Public License) Price:
819 downloads
Net::FreeDB2::Connection 0.8.2.6
Net::FreeDB2::Connection is a FreeDB/CDDB abstract connection class. more>>
Net::FreeDB2::Connection is a FreeDB/CDDB abstract connection class.
Net::FreeDB2::Connection is an abstract class to represent connections to FreeDB/CDDB servers. After a successfull connection, FreeDB/CDDB queries, reads etc can be made to obtain/provide information from/to FreeDB/CDDB databases.
CONSTRUCTOR
new (OPT_HASH_REF)
Creates a new Net::FreeDB2::Connection object. By default connect () is called to initiate the connection but see option no_connect. See the implementation for complements/restrictions.
Options for OPT_HASH_REF may include:
client_name
Mandatory option to name the connecting client software.
client_version
Mandatory option with the client software version string.
client_host
The hostname of the client. Defaults to &Sys::Hostname::hostname ().
client_user
The user of the client. Defaults to scalar (getpwuid ($>));
freedb_host
The FreeDB/CDDB host. Defaults to freedb.freedb.org.
freedb_port
The port on the FreeDB/CDDB host.
proxy_host
Proxy host.
proxy_port
Port on the proxy host. Defaults to 8080.
proxy_user
Proxy user name to use.
proxy_passwd
Proxy password to use.
no_connect
Do not call connect () during instanciation.
<<lessNet::FreeDB2::Connection is an abstract class to represent connections to FreeDB/CDDB servers. After a successfull connection, FreeDB/CDDB queries, reads etc can be made to obtain/provide information from/to FreeDB/CDDB databases.
CONSTRUCTOR
new (OPT_HASH_REF)
Creates a new Net::FreeDB2::Connection object. By default connect () is called to initiate the connection but see option no_connect. See the implementation for complements/restrictions.
Options for OPT_HASH_REF may include:
client_name
Mandatory option to name the connecting client software.
client_version
Mandatory option with the client software version string.
client_host
The hostname of the client. Defaults to &Sys::Hostname::hostname ().
client_user
The user of the client. Defaults to scalar (getpwuid ($>));
freedb_host
The FreeDB/CDDB host. Defaults to freedb.freedb.org.
freedb_port
The port on the FreeDB/CDDB host.
proxy_host
Proxy host.
proxy_port
Port on the proxy host. Defaults to 8080.
proxy_user
Proxy user name to use.
proxy_passwd
Proxy password to use.
no_connect
Do not call connect () during instanciation.
Download (0.030MB)
Added: 2007-03-05 License: Perl Artistic License Price:
965 downloads
LineControl Server 2.1.21
LineControl allows you to remotely control the Internet connection of a Linux masquerading server using multiple clients. more>>
LineControl allows you to remotely control the Internet connection of a Linux masquerading server using multiple clients. It takes care with the number of clients using the connection and decides upon this number whether the connection should be up or down.
The clients show the time the connection is up and throughput statistics. Different connection types are supported, such as analog modems, ISDN, or even cable modems and ADSL devices.
Main features:
- user accounting using Linux-PAM or passwd/shadow file
- controlling multiple lines
- throughput measuring
- logging & analizing (view example)
- logging to a MySQL database (view example)
- html formatted status report via webserver (view example)
- different line types (analog, isdn, adsl, ... it should be possible to run LC with any line!)
- pinger (to avoid line-drops)
- reporting data (time, nr, ...) about incoming isdn calls to the clients (inclusive addressbook lookup)
- client dependant modifications of the NAT servers firewall (using an external script whenever a client goes on- or offline)
<<lessThe clients show the time the connection is up and throughput statistics. Different connection types are supported, such as analog modems, ISDN, or even cable modems and ADSL devices.
Main features:
- user accounting using Linux-PAM or passwd/shadow file
- controlling multiple lines
- throughput measuring
- logging & analizing (view example)
- logging to a MySQL database (view example)
- html formatted status report via webserver (view example)
- different line types (analog, isdn, adsl, ... it should be possible to run LC with any line!)
- pinger (to avoid line-drops)
- reporting data (time, nr, ...) about incoming isdn calls to the clients (inclusive addressbook lookup)
- client dependant modifications of the NAT servers firewall (using an external script whenever a client goes on- or offline)
Download (0.20MB)
Added: 2005-09-19 License: GPL (GNU General Public License) Price:
1496 downloads
BitWise Routing Server for Linux 1.7
allows you to accept BitWise connections to multiple computers behind a router. more>> The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.
As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.
The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).<<less
Download (1011KB)
Added: 2009-04-20 License: Freeware Price: Free
187 downloads
GroundWork Monitor Community Edition 5.3.0 GA
GroundWork Monitor Community Edition offers you an ideal IT monitoring solution to maintain network visibility and control. more>> <<less
Added: 2009-02-11 License: GPL Price: FREE
1 downloads
Net::Server 0.93
Net::Server is an extensible, general Perl server engine. more>>
Net::Server is an extensible, general Perl server engine.
SYNOPSIS
#!/usr/bin/perl -w -T
package MyPackage;
use Net::Server;
@ISA = qw(Net::Server);
sub process_request {
#...code...
}
MyPackage->run(port => 160);
exit;
Main features:
- Single Server Mode
- Inetd Server Mode
- Preforking Simple Mode (PreForkSimple)
- Preforking Managed Mode (PreFork)
- Forking Mode
- Multiplexing Mode using a single process
- Multi port accepts on Single, Preforking, and Forking modes
- Simultaneous accept/recv on tcp, udp, and unix sockets
- Safe signal handling in Fork/PreFork avoids perl signal trouble
- User customizable hooks
- Chroot ability after bind
- Change of user and group after bind
- Basic allow/deny access control
- Customized logging (choose Syslog, log_file, or STDERR)
- HUP able server (clean restarts via sig HUP)
- Dequeue ability in all Fork and PreFork modes.
- Taint clean
- Written in Perl
- Protection against buffer overflow
- Clean process flow
- Extensibility
Net::Server is an extensible, generic Perl server engine. Net::Server combines the good properties from Net::Daemon (0.34), NetServer::Generic (1.03), and Net::FTPServer (1.0), and also from various concepts in the Apache Webserver.
Net::Server attempts to be a generic server as in Net::Daemon and NetServer::Generic. It includes with it the ability to run as an inetd process (Net::Server::INET), a single connection server (Net::Server or Net::Server::Single), a forking server (Net::Server::Fork), a preforking server which maintains a constant number of preforked children (Net::Server::PreForkSimple), or as a managed preforking server which maintains the number of children based on server load (Net::Server::PreFork). In all but the inetd type, the server provides the ability to connect to one or to multiple server ports.
Net::Server uses ideologies of Net::FTPServer in order to provide extensibility. The additional server types are made possible via "personalities" or sub classes of the Net::Server. By moving the multiple types of servers out of the main Net::Server class, the Net::Server concept is easily extended to other types (in the near future, we would like to add a "Thread" personality).
Net::Server borrows several concepts from the Apache Webserver. Net::Server uses "hooks" to allow custom servers such as SMTP, HTTP, POP3, etc. to be layered over the base Net::Server class. In addition the Net::Server::PreFork class borrows concepts of min_start_servers, max_servers, and min_waiting servers.
Net::Server::PreFork also uses the concept of an flock serialized accept when accepting on multiple ports (PreFork can choose between flock, IPC::Semaphore, and pipe to control serialization).
<<lessSYNOPSIS
#!/usr/bin/perl -w -T
package MyPackage;
use Net::Server;
@ISA = qw(Net::Server);
sub process_request {
#...code...
}
MyPackage->run(port => 160);
exit;
Main features:
- Single Server Mode
- Inetd Server Mode
- Preforking Simple Mode (PreForkSimple)
- Preforking Managed Mode (PreFork)
- Forking Mode
- Multiplexing Mode using a single process
- Multi port accepts on Single, Preforking, and Forking modes
- Simultaneous accept/recv on tcp, udp, and unix sockets
- Safe signal handling in Fork/PreFork avoids perl signal trouble
- User customizable hooks
- Chroot ability after bind
- Change of user and group after bind
- Basic allow/deny access control
- Customized logging (choose Syslog, log_file, or STDERR)
- HUP able server (clean restarts via sig HUP)
- Dequeue ability in all Fork and PreFork modes.
- Taint clean
- Written in Perl
- Protection against buffer overflow
- Clean process flow
- Extensibility
Net::Server is an extensible, generic Perl server engine. Net::Server combines the good properties from Net::Daemon (0.34), NetServer::Generic (1.03), and Net::FTPServer (1.0), and also from various concepts in the Apache Webserver.
Net::Server attempts to be a generic server as in Net::Daemon and NetServer::Generic. It includes with it the ability to run as an inetd process (Net::Server::INET), a single connection server (Net::Server or Net::Server::Single), a forking server (Net::Server::Fork), a preforking server which maintains a constant number of preforked children (Net::Server::PreForkSimple), or as a managed preforking server which maintains the number of children based on server load (Net::Server::PreFork). In all but the inetd type, the server provides the ability to connect to one or to multiple server ports.
Net::Server uses ideologies of Net::FTPServer in order to provide extensibility. The additional server types are made possible via "personalities" or sub classes of the Net::Server. By moving the multiple types of servers out of the main Net::Server class, the Net::Server concept is easily extended to other types (in the near future, we would like to add a "Thread" personality).
Net::Server borrows several concepts from the Apache Webserver. Net::Server uses "hooks" to allow custom servers such as SMTP, HTTP, POP3, etc. to be layered over the base Net::Server class. In addition the Net::Server::PreFork class borrows concepts of min_start_servers, max_servers, and min_waiting servers.
Net::Server::PreFork also uses the concept of an flock serialized accept when accepting on multiple ports (PreFork can choose between flock, IPC::Semaphore, and pipe to control serialization).
Download (0.080MB)
Added: 2006-06-27 License: Perl Artistic License Price:
1219 downloads
BitWise Routing Server 1.7
BitWise Routing Server allows multiple PCs behind a router to make direct connections. more>>
BitWise Routing Server allows multiple PCs behind a router to make direct connections.
The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.
As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.
The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).
The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.
The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.
Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.
In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.
If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.
Setting up the physical router
The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.
The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).
Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.
Configuring BitWise to use the Routing Server
In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).
Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.
Registration with the Routing Server
Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.
It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.
Using the Routing Server
Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.
The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.
<<lessThe BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.
As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.
The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).
The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.
The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.
Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.
In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.
If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.
Setting up the physical router
The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.
The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).
Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.
Configuring BitWise to use the Routing Server
In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).
Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.
Registration with the Routing Server
Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.
It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.
Using the Routing Server
Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.
The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.
Download (1.0MB)
Added: 2006-03-02 License: Freeware Price:
1331 downloads
GetMonitor 0.5
GetMonitor is a Python XChat script for monitoring DCC file servers requests on sharing channels and IRC servers. more>>
GetMonitor project is a Python XChat script for monitoring DCC file servers requests on sharing channels and IRC servers.
Similar to AutoGet and SDFind scripts, it helps you request files, monitor queues, and search files automatically.
<<lessSimilar to AutoGet and SDFind scripts, it helps you request files, monitor queues, and search files automatically.
Download (0.006MB)
Added: 2007-08-24 License: GPL (GNU General Public License) Price:
797 downloads
Interprocess Communication Server(unix) 1.07
Interprocess synchronization and communication primitives for C++ more>> RIPC is library providing interprocess synchronization and communication capabilities for processes running at different network nodes. RIPC provides wide set of standard primitives: semaphore, event, FIFO queue, barrier, shared memory, shared and exclusive locks.
Structure of RIPC package
RIPC package consists of two libraries:
ripcclient.lib
Provides stubs of RIPC primitives sending requests to the server
ripcserver.lib
Server implementation of RIPC primitives
RIPC supports local and remote sessions. Remote sessions created by RIPCClientFactory class establish connection with the server through TCP/IP stream socket. Server process should be started before clients. In this case primitives at local computer servers as stubs and redirect requests to the server. This mode is useful to provide synchronization and communication between several processes at the same or different computers.
Local sessions are created by RIPCServerFactory class. Them are useful to provide synchronization of threads within the same process (if you want to use more sophisticated synchronization primitives than standard synchronization facilities provided by OS). The single local session can be shared by all threads. No server process should be started in this case.
Quick start
Include files needed for use of RIPC package are located in inc directory. Libraries are located in lib directory. Version of RIPC for windows is provided with binaries of these librarier and server built by Visual C++ comiler. At all other system you will have to build these libraries yourself. Change directory to src and exceute make (for Visual C++ RIPC provides make.bat file which invokes MS nmake utility for makefile.mvc). By default static version of librarier are built. To produce dynamically linked librariers, edit makefile and assign set GENERATE_DLL=1. In case of using DLL libraries do not forget to include them in PATH (at Windows) or in LD_LIBRARY_PATH (at Unix).<<less
Download (106KB)
Added: 2009-04-16 License: Freeware Price: Free
190 downloads
dotDefender Monitor for Apache 3.84
dotDefender Monitor for Apache is the only way to know who is attacking your web site in real time. Residing on the server as webserver plug-in, dotDefender can be installed and implemented in minutes without influence on traffic or network archite more>> <<less
Download (17.17MB)
Added: 2009-04-10 License: Freeware Price:
196 downloads
FTP Monitor 0.8
FTP Monitor its a simple panel applet, which monitors incoming connections to ftpd. more>>
FTP Monitor is a simple panel applet, which monitors incoming connections to ftpd(vsftpd/ncftpd/pure-ftpd/proftpd) and generates passive popups.
For pure-ftpd, ncftpd, proftpd it acts as a frontend to pure-ftpwho, ncftpd_spy and ftpwho respectively. For vsftpd, it looks in output of ps -fe.
Enhancements:
- Update the change in ftp daemon (or path) withour requiring a restart
- Fixed the bug (introduced in 0.70) that FTP status will not update
- For large panels, the icon is now centered
<<lessFor pure-ftpd, ncftpd, proftpd it acts as a frontend to pure-ftpwho, ncftpd_spy and ftpwho respectively. For vsftpd, it looks in output of ps -fe.
Enhancements:
- Update the change in ftp daemon (or path) withour requiring a restart
- Fixed the bug (introduced in 0.70) that FTP status will not update
- For large panels, the icon is now centered
Download (0.85MB)
Added: 2005-12-23 License: GPL (GNU General Public License) Price:
1441 downloads
NoMachine NX Server Manager 3.0.0-28
NoMachine NX Server Manager is the upcoming management interface for the NX Terminal Server system. more>>
NoMachine NX Server Manager is the upcoming management interface for the NX Terminal Server system.
The NX Server Manager is the easy-to-use NoMachine graphical administration interface for Unix systems that allows administrators to configure, manage and monitor the NX servers across a world-wide network.
The NX Server Manager is an add-on to the NX Server Enterprise and Small Business Edition, provided at no extra cost.
The NX Server Manager sports most of the features you would expect from an enterprise-grade application, with the easiness of use of a Web interface.
NoMachine NX is a fast terminal server system based on the X11 protocol. In addition, NX also translates and embeds the MS Windows Terminal Server and VNC protocols into X/NX.
By embedding RDP and RFB, it enables users to compress and accelerate remote Windows and VNC sessions. NX lets you work fluently even across slow links like modems.
The NX project provides a suite of libraries and X11 proxying agents implementing efficient compression and optimized transport of X11, SMB, IPP, HTTP, and arbitrary protocols like audio over the Internet.
Enhancements:
- This release provides fixes for a number of problems: the NX Server Manager setup script looked for a nonexistant file during the install or upgrade procedure, reloading the NX statistics Web page may have failed, and NX Server Manager may have provided a misleading message when NX statistics couldnt be generated.
<<lessThe NX Server Manager is the easy-to-use NoMachine graphical administration interface for Unix systems that allows administrators to configure, manage and monitor the NX servers across a world-wide network.
The NX Server Manager is an add-on to the NX Server Enterprise and Small Business Edition, provided at no extra cost.
The NX Server Manager sports most of the features you would expect from an enterprise-grade application, with the easiness of use of a Web interface.
NoMachine NX is a fast terminal server system based on the X11 protocol. In addition, NX also translates and embeds the MS Windows Terminal Server and VNC protocols into X/NX.
By embedding RDP and RFB, it enables users to compress and accelerate remote Windows and VNC sessions. NX lets you work fluently even across slow links like modems.
The NX project provides a suite of libraries and X11 proxying agents implementing efficient compression and optimized transport of X11, SMB, IPP, HTTP, and arbitrary protocols like audio over the Internet.
Enhancements:
- This release provides fixes for a number of problems: the NX Server Manager setup script looked for a nonexistant file during the install or upgrade procedure, reloading the NX statistics Web page may have failed, and NX Server Manager may have provided a misleading message when NX statistics couldnt be generated.
Download (2.3MB)
Added: 2007-08-03 License: Other/Proprietary License Price:
819 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above monitor server connections search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
