Skip to Content.
Sympa Menu

freetds - Re: [freetds] Comment required...

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Comment required...
  • Date: Thu, 29 Mar 2007 16:30:48 +0200

> >
> >
> > I'd like to apply this patch.
> >
> > The intention is to apply (at least partially) fix for
> >
> http://sourceforge.net/tracker/index.php?func=detail&aid=14310
> 50&group_i
> > d=33106&atid=407808 (SSL enhancements patch at SourceForge).
>
> Hi Freddy,
>
> Thank you for taking care of this. My suggestions regard some of the
> names:
>
> s/encrypt_level/encryption_level/ (longer, maybe clearer, up to you).
>
> s/tds_config_crypt/tds_config_encryption/ (much clearer IMO).
>

no problem, committed, changed all (en)crypt to encription

> Not to punish a good deed, but we need a UG section, too.
>

anf anf...

This can be a start

diff -u -1 -0 -r1.97 userguide.sgml
--- doc/userguide.sgml 12 Apr 2006 19:40:23 -0000 1.97
+++ doc/userguide.sgml 29 Mar 2007 14:27:46 -0000
@@ -931,20 +931,26 @@
<note><para>This requires an extra round-trip with
server and may thus slightly delay making the
connection.</para></note></para></entry>
<entry>instance name</entry>
</row>
<row>
<entry>debug flags</entry>
<entry>0x4fff</entry>
<entry>Sets granularity of logging. A set of bit that specify
levels and informations.
See table below for bit specification.</entry>
<entry>any number even in hex or octal notation</entry>
</row>
+ <row>
+ <entry>encryption</entry>
+ <entry>off</entry>
+ <entry>Specify if encryption is desidered. Supported under
mssql. Off disable encryption (only if needed), request use if
available, required only make encrypted connections.</entry>
+ <entry>off/request/required</entry>
+ </row>
</tbody>
</tgroup>
</table>

<para>The logging capability has help solve inumerable cases,
some trivial and some very low-level bugs. Sometimes a developer needs
very detailed information about one function, whereas at other times
someone may interested only in whether or not a particular function is
called, or even want to see only the SQL that was transmitted to the
server. </para>

<para>The log's granularity can be controlled with the <literal>debug
flags</> entry. The default value (<literal>4FFF</> hex) gives a level
of detail that is useful for resolving problems via the mailing list.
</para>

<table id="tab.freetds.conf.debugflags">
<title>Valid bitmask values for <literal>debug flags</> entry in
<filename>freetds.conf</filename></title>

bye
freddy77





Archive powered by MHonArc 2.6.24.

Top of Page