Gecko [ www.thearyasamaj.org ]

Name	Size	Permission
ftpasswd.html	14.61 KB	-rw-r--r--
ftpmail.html	8 KB	-rw-r--r--
ftpquota.html	10.9 KB	-rw-r--r--
index.html	9.04 KB	-rw-r--r--
mod_auth_otp.html	16.5 KB	-rw-r--r--
mod_ban.html	22.53 KB	-rw-r--r--
mod_copy.html	4.85 KB	-rw-r--r--
mod_ctrls_admin.html	15.05 KB	-rw-r--r--
mod_deflate.html	6.89 KB	-rw-r--r--
mod_digest.html	12.92 KB	-rw-r--r--
mod_dnsbl.html	6.1 KB	-rw-r--r--
mod_dynmasq.html	3.26 KB	-rw-r--r--
mod_exec.html	23.89 KB	-rw-r--r--
mod_geoip.html	17.06 KB	-rw-r--r--
mod_ifsession.html	11.02 KB	-rw-r--r--
mod_ifversion.html	4.96 KB	-rw-r--r--
mod_ldap.html	32.32 KB	-rw-r--r--
mod_load.html	2.97 KB	-rw-r--r--
mod_log_forensic.html	9.78 KB	-rw-r--r--
mod_qos.html	2.62 KB	-rw-r--r--
mod_quotatab.html	25.02 KB	-rw-r--r--
mod_quotatab_file.html	2.23 KB	-rw-r--r--
mod_quotatab_ldap.html	2.63 KB	-rw-r--r--
mod_quotatab_radius.html	2.08 KB	-rw-r--r--
mod_quotatab_sql.html	10.93 KB	-rw-r--r--
mod_radius.html	22.11 KB	-rw-r--r--
mod_ratio.html	6.99 KB	-rw-r--r--
mod_readme.html	2.69 KB	-rw-r--r--
mod_rewrite.html	30.06 KB	-rw-r--r--
mod_sftp.html	93.71 KB	-rw-r--r--
mod_sftp_pam.html	5.47 KB	-rw-r--r--
mod_sftp_sql.html	5.63 KB	-rw-r--r--
mod_shaper.html	23.28 KB	-rw-r--r--
mod_site_misc.html	5.81 KB	-rw-r--r--
mod_snmp.html	42.38 KB	-rw-r--r--
mod_sql.html	62.81 KB	-rw-r--r--
mod_sql_odbc.html	10.2 KB	-rw-r--r--
mod_sql_passwd.html	24.44 KB	-rw-r--r--
mod_sql_sqlite.html	2.95 KB	-rw-r--r--
mod_statcache.html	8.29 KB	-rw-r--r--
mod_tls.html	85.34 KB	-rw-r--r--
mod_tls_fscache.html	2.73 KB	-rw-r--r--
mod_tls_memcache.html	3.91 KB	-rw-r--r--
mod_tls_redis.html	3.6 KB	-rw-r--r--
mod_tls_shmcache.html	6.78 KB	-rw-r--r--
mod_unique_id.html	3.54 KB	-rw-r--r--
mod_wrap.html	12.38 KB	-rw-r--r--
mod_wrap2.html	24.83 KB	-rw-r--r--
mod_wrap2_file.html	4.69 KB	-rw-r--r--
mod_wrap2_redis.html	5.33 KB	-rw-r--r--
mod_wrap2_sql.html	8.33 KB	-rw-r--r--

Code Editor : mod_sql_odbc.html

<!DOCTYPE html>
<html>
<head>
<title>ProFTPD module mod_sql_odbc</title>
</head>

<hr> 
<center>
<h2>ProFTPD module <code>mod_sql_odbc</code></h2>
</center>
<hr>

ODBC means Open Database Connectivity, and defines
a standard way of connecting to a database server such as MySQL, Postgres,
SQL Server, Oracle, etc. Many of the these databases also provide
their own native APIs for connectivity, in addition to supporting ODBC. Other
databases provide ODBC support, but no support for native connectivity.

The ProFTPD distribution includes the <code>mod_sql_mysql</code> module for
talking to a MySQL database using the native MySQL API, and a
<code>mod_sql_postgres</code> for connecting to Postgres databases using the
native Postgres API. However, there was no support for databases other
than these -- until now. The purpose of the <code>mod_sql_odbc</code> module
is to allow ProFTPD's <code>mod_sql</code> module to connect to any
database that supports ODBC. This module also allows proftpd to work with
databases that may already provide APIs for native connectivity, but for
which a specific <code>mod_sql</code> has not yet been developed.

This module is contained in the <code>mod_sql_odbc.c</code> file for
ProFTPD 1.3.x, and is not compiled by default. Installation
instructions are discussed <a href="#Installation">here</a>.

The most current version of <code>mod_sql_odbc</code> is distributed with
ProFTPD.

<h2>Author</h2>

Please contact TJ Saunders &lt;tj at castaglia.org&gt; with any
questions, concerns, or suggestions regarding this module.

<h2>Directives</h2>
<ul>
 <li><a href="#SQLODBCVersion">SQLODBCVersion</a>
</ul>

<hr>
<h3><a name="SQLODBCVersion">SQLODBCVersion</a></h3>
Syntax: SQLODBCVersion version 
Default: SQLODBCVersion ODBCv3 
Context: server config, <code>&lt;VirtualHost&gt;</code>, <code>&lt;Global&gt;</code> 
Module: mod_sql_odbc 
Compatibility: 1.3.6rc2 and later

The <code>SQLODBCVersion</code> directive configures the ODBC API
version that the ODBC driver should use/expect. The default is
"ODBCv3", i.e. ODBC version 3. Some drivers may have issues with the
default version; this can manifest as errors similar to the following in your
<code>SQLLogFile</code>:
<pre>
 message: '[unixODBC][Driver Manager]Driver does not support the requested version'
</pre>
When this happens, you might try using an older version of ODBC, via:
<pre>
 SQLODBCVersion ODBCv2
</pre>

<hr>
<h2><a name="Installation">Installation</a></h2>
The <code>mod_sql_odbc</code> relies on one of the two following libraries
for ODBC support:
<pre>
 <a href="http://www.iodbc.org">http://www.iodbc.org</a>
 <a href="http://www.unixodbc.org">http://www.unixodbc.org</a>
</pre>
One of these ODBC libraries must be installed prior to using
<code>mod_sql_odbc</code>.

Follow the usual steps for using contrib modules in ProFTPD, making sure to
list <code>mod_sql</code>. Note that you will need to use the
<code>LIBS</code> environment variable for indicating which ODBC library
to link against.

For example, if you wish to use the unixODBC library, you would use:
<pre>
 $ ./configure LIBS=-lodbc --with-modules=mod_sql:mod_sql_odbc ...
 $ make
 $ make install
</pre>
On the other hand, for using the iODBC library, the invocation is slightly
different, specifying a different library name:
<pre>
 $ ./configure LIBS=-liodbc --with-modules=mod_sql:mod_sql_odbc ...
 $ make
 $ make install
</pre>

You may need to specify the location of the ODBC header and library files in
your <code>configure</code> command, e.g.:
<pre>
 $ ./configure \
 LD_LIBRARY_PATH=/usr/local/odbc/lib \
 LDFLAGS=-L/usr/local/odbc/lib \
 LIBS=-lodbc \
 --with-modules=mod_sql:mod_sql_odbc \
 --with-includes=/usr/local/odbc/include \
 --with-libraries=/usr/local/odbc/lib
</pre>

<hr>
<h2><a name="Usage">Usage</a></h2>
Note: some of the following information is taken from:
<pre>
 <a href="http://www.mysql.com/products/myodbc/manual.html#Introduction_to_ODBC">http://www.mysql.com/products/myodbc/manual.html#Introduction_to_ODBC</a>
</pre>

What is ODBC? 
ODBC (Open Data Base Connectivity) provides a way
for client programs to access a wide range of databases or data sources.

ODBC is a standardized API, developed according to the specifications of the
SQL Access Group, that allows one to connect to SQL databases. It defines a
set of function calls, error codes and data types that can be used to develop
database-independent applications. ODBC is usually used when database
independence, or simultaneous access to different data sources, is required.

For more information about ODBC, refer to:
<pre>
 http://www.microsoft.com/data/odbc/
</pre>

When should <code>mod_sql_odbc</code> be used? 
There are two cases where a site might need to use the <code>mod_sql_odbc</code>
module: when the site's database does not provide a native connectivity API
(e.g. FrontBase), and when the site's database does not have a
corresponding <code>mod_sql_db</code> module for it. For example,
ProFTPD does not have a <code>mod_sql_oracle</code> module. Using
<code>mod_sql_odbc</code> and an Oracle-provided ODBC driver would allow
a site to have <code>proftpd</code> communicate with their Oracle database.

How does ODBC work? 
An ODBC driver is a dynamically loadable library that knows how to
talk to a specific database. Many databases come bundled with an ODBC
driver. The following lists where to find ODBC drivers for the popular
MySQL and Postgres databases:
<dl>
 <dt>MySQL ODBC Driver (MyODBC)</dt>
 <dd><a href="http://www.mysql.com/products/myodbc/">http://www.mysql.com/products/myodbc/</a></dd>

<dt>Postgres ODBC Driver (psqlODBC)</dt>
 <dd><a href="https://odbc.postgresql.org/">https://odbc.postgresql.org/</a></dd>
</dl>

The ODBC driver manager is a library that manages communication between
the ODBC-aware application and ODBC drivers. Its main functionality includes: 
<ul>
 <li>resolving Data Source Names (DSN) 
 <li>loading and unloading of the drivers 
 <li>processing ODBC function calls or passing them to the driver 
</ul>
The following lists some commonly used driver managers: 
<dl>
 <dt>iODBC ODBC Driver Manager for Unix</dt>
 <dd><a href="http://www.iodbc.org">http://www.iodbc.org</a></dd>

<dt>unixODBC Driver Manager for Unix</dt>
 <dd><a href="http://www.unixodbc.org">http://www.unixodbc.org</a></dd>

<dt>Microsoft Windows ODBC Driver Manager</dt>
 <dd><a href="http://www.microsoft.com/data/">http://www.microsoft.com/data/</a></dd>
</dl>

Environment Variables 
There are two environment variables that both the iODBC and unixODBC libraries
use: <code>LD_LIBRARY_PATH</code> and <code>ODBCINI</code>. The
<code>ODBCINI</code> environment variable specifies the configuration file
used by the library; this file specifies the driver to use, and any database
connection information that driver may need.The <code>LD_LIBRARY_PATH</code>
environment variable is used to tell the Driver Manager where it may find
the driver libraries. Note that on a Linux system, if the
<code>/etc/ld.so.conf</code> contains the directory where the ODBC driver
libraries live (and <code>/sbin/ldconfig</code> has been run), use of
the <code>LD_LIBRARY_PATH</code> setting may not be necessary.

Configuring ODBC 
The hard part about using the iODBC or unixODBC Unix driver managers is
their configuration. Often in ODBC documentation you will mention of DSNs,
or Data Source Names. A data source identifies a path to data that can include
a network library, server, database, and other attributes. To connect to a data
source, the driver manager checks for specific connection information. This
specific connection information is recorded in a file usually called
&quot;odbc.ini&quot;.

Example iODBC <code>odbc.ini</code> file:
<pre>
 [ODBC Data Sources]
 mysql = MySQL ODBC Connector (MyODBC)

[mysql]
 Driver = /usr/local/iodbc/lib/libmyodbc3.so
 Description = MySQL Driver
 Server = localhost
 Database = proftpd
 Port = 3306
 Socket = /tmp/mysql.sock
</pre>

Example unixODBC <code>odbc.ini</code> file:
<pre>
 [mysql]
 Description = MySQL
 Driver = mysql
 Server = localhost
 Database = proftpd
 Port = 3306
 Socket = /tmp/mysql.sock
</pre>

More details on the contents of <code>odbc.ini</code> files, and the different
meanings of configuration options, can be found in the respective driver
manager documentation.

Configuring <code>mod_sql_odbc</code> 
For the most part, <code>mod_sql_odbc</code> requires little configuration.
It relies on the ODBC driver managers, which in turn use the above
environment variables. This means that <code>ODBCINI</code> and
<code>LD_LIBRARY_PATH</code> can be set in the environment, before starting
<code>proftpd</code>, and <code>mod_sql_odbc</code> would then work. The
one required bit of information is the
<a href="mod_sql.html#SQLConnectInfo"><code>SQLConnectInfo</code></a> directive.
This directive needs to contain the name of the stanza in your
<code>odbc.ini</code> file which holds the configuration. Using the example
<code>odbc.ini</code> files above, you would need the following in your
<code>proftpd.conf</code>:
<pre>
 # Tells mod_sql to use mod_sql_odbc
 SQLBackend odbc

# Tells mod_sql_odbc which odbc.ini stanza to use
 SQLConnectInfo mysql
</pre>

Starting with proftpd 1.2.10rc1, it is possible to use the <code>SetEnv</code>
configuration directives to set the environment variables directly in
the <code>proftpd.conf</code> file, which makes configuration more
centralized.

Example configuration using <code>SetEnv</code>:
<pre>
 &lt;IfModule mod_sql_odbc.c&gt;
 SetEnv LD_LIBRARY_PATH /path/to/odbc/lib
 SetEnv ODBCINI /path/to/<code>odbc.ini</code>
 &lt;/IfModule&gt;
</pre>
Please contact the author directly with any questions or comments.

</body>
</html>

${this.title}

Code Editor : mod_sql_odbc.html