Free sql server connections software for linux

SQL-Ledger Accounting project is a double entry accounting system. Accounting data is stored in a SQL Server, for the display any text or GUI browser can be used. The entire system is linked through a chart of accounts. Each item in inventory is linked to income, expense, inventory and tax accounts. When items are sold and purchased the accounts are automatically updated.
With the assembly feature you can build manufactured goods from parts, services, labor units and assemblies. When the assembly is sold all the accounts linked to the individual parts, services, labor units and assemblies are updated and stock levels adjusted accordingly.
Invoices, Packing List, Income Statement, Balance Sheet, Sales, Work and Purchase Order, Statements, Receipts and Checks are generated from templates and can be changed to suit your needs. Templates are provided in html, tex and text format. The tex templates are processed with latex to produce postscript and PDF documents. Documents can be sent to a printer, file or fax, displayed with a PDF viewer or sent by email.
The translation mechanism for items and foreign language templates can be set for each customer/vendor so it is possible to generate invoices in a foreign language without knowledge of a foreign language. This translation facility can also be used to generate different forms for a group of customers/vendors.
DWS Systems Inc. is the developer of SQL-Ledger and provides ongoing support and customizations. SQL-Ledger is licensed under the GPL license, and is free software.
SQL-Ledger can be used on any UNIX, Mac OS X and Windows computer.
SQL-Ledger is written in Perl, developed on FreeBSD and Linux with Galeon, Konqueror, Netscape, Lynx, Links, W3M, Voyager, Explorer to render the display, Apache, thttpd, boa to communicate between the server and the browser, and PostgreSQL, Oracle, or DB2 to store accounting data.
Languages:
- English
- Arabic (Egypt)
- Bahasa Indonesia
- Brazilian Portuguese
- Catalan
- Chinese (Simplified)
- Chinese (Traditional)
- Czech
- Danish
- Dutch
- Estonian
- Finnish
- French
- German
- Greek
- Hungarian
- Icelandic
- Italian
- Latvian
- Lithuanian
- Norwegian
- Polish
- Portuguese
- Russian
- Spanish
- Swedish
- Turkish
- Ukrainian
Main features:
- Accounts Receivable
- Accounts Payable
- General Ledger
- Inventory Control
- Billing / Invoicing
- Time Cards
- Recurring Invoices
- POS
- Check Printing
- Purchase / Sales Orders
- Customizable Taxes
- Multi-user
- Multi-company
- Audit Control
- Foreign Currency
- Internationalization
- Access Control
- SQL server backend
- Customizable Templates
- Customers
- Vendors
- Assemblies (BOM, kits)
- Chart of Accounts
- Customizable Reports
- Financial Statements
- Administration Module
- Backup to file/email
- Application Interface
- Use on Handheld

Streamnik Server project is an IPTV server based on the open codecs Ogg/Vorbis and Ogg/Theora. It can stream a number of different channels and is optimized to run on leased (virtual) servers. The program schedule is defined by an SQL database table and can be changed at runtime.

SS5 is a socks server that implements the SOCKS v4 and v5 protocol. As a proxy server, SS5 authenticates, profiles and processes network requests for clients.
Socks Server 5 establishes connections to application hosts for client applications. When the client attempts to access the network, the client connects to the SS5 daemon instead of the application host.
Following authentication, clients request that SS5 perform network activities for the client.
The activities might include:
CONNECT
BIND
UDP ASSOCIATE
The SS5 protocol is independent of application protocols, and can assist with different networking services, including telnet, ftp, finger, whois, gopher, and WWW access.
Enhancements:
- Fix code

EasyEclipse Server Java is for development of server-side Java applications, such as JavaServer Pages, EJBs and Web Services.
EasyEclipse Server Edition contains lots of plugins to manage different application servers (Tomcat, JBoss, WebLogic), develop on some server-side frameworks (Struts, Java Server Faces), and manipulate common file types on servers (HTML, XML, JSPs).
This distribution includes the following plugins:
Core components with a JDK:
- Eclipse Platform 3.2.1 - Shared platform services from Eclipse.
- Eclipse Tools 3.2.1 - Common libraries for various Eclipse projects.
- Java JDK for Windows 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java JDK for Linux 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general Java development:
- Eclipse Java Development Tools 3.2.1 - Edit, compile, run, debug, test, refactor, document and deploy Java applications.
Some essential utilities:
- AnyEdit Tools 1.5.6.2 - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", et cetera.
- Eclipse Utils Plugins 1.0.0.1 - Save the cursor position of editors when closing and re-opening a file. Access common team actions with explorer buttons.
- Color Editor 1.2.4 - Edit with syntax highlighting over 100+ file formats.
Tools for development of server-side applications in Java:
- Sysdeo Tomcat Launcher 3.2.0.beta - Start, stop, and manage Tomcat and WAR files without leaving Eclipse.
- JBoss IDE with AOP and EJB3 2.0.0.Beta2 - Develop, deploy, test and debug JBoss-based applications, with support of Enterprise Java Beans 3.0 and Aspect-Oriented Programming.
- Hibernate Tools 3.2.0.beta8 - Edit Hibernate mappings, execute HQL queries and develop applications with Hibernate, a Java persistence and object-relational mapping framework.
- Weblogic Server Plugin for Eclipse 2.0.0.RC3-1 - Start, stop and manage a WebLogic server. Run and debug applications on a Weblogic server.
- Spring IDE 1.3.6 - Develop, manage and deploy Spring Framework based applications.
- Eclipse J2EE tools 1.5.2 - Create and deploy J2EE based applications, including Servlets, JSP and EJB.
- Eclipse Database tools 1.5.2 - Access, manage and query SQL relational databases and servers.
- Amateras IDE 2.0.2 - Edit HTML, XML and JSP. Manage Struts and Java Server Faces configuration files visually.
Tools for web development:
- Eclipse Web tools editors 1.5.2 - Edit and validate XML, XSL, XML Schemas, DTD, HTML, JavaScript and CSS files. Test and validate web services.
- Eclipse HTML Tidy 1.2.2.patch-01-1 - Format and validate HTML, XHTML and XML documents within your favorite editor.
- Amateras HTML and XML editor 2.0.2 - Edit HTML, JSP, XML and CSS files.
Database management tool:
- QuantumDB 3.0.3 - Access, manage and query SQL relational database and servers access using standard JDBC drivers.
Version Control tools (note that CVS support is included in the Eclipse Platform):
- Subclipse 1.1.8 - Access and manage Subversion repositories within Eclipse.

conn-close gives us possibility to get rid of entries in ip_conntrack about ESTABLISHED TCP connections that goes through our server.

conn-close script uses hping2 to send spoofed RST packets which will fool conntrack and cause specified connections to be considered by conntrack as closed (now these connections will be in ip_conntrack in CLOSE state), even though RST packets will be more likely discarded by destination host.

Information about connections is read of course from /proc/net/ip_conntrack.

Idea was taken from script seen somewhere on the internet.

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.

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).