Changes between Version 4 and Version 5 of DatabaseBasedAnalysis/Connection

Timestamp:

08/04/18 18:20:27 (6 years ago)

Author:

tbretz

Comment:

--

DatabaseBasedAnalysis/Connection

@@ -7 +7 @@
 A connection from everywhere is allowed, if the connection is '''encrypted'''. Connections from ihp-pc45 might be unencrypted.
 
-For the mysql client the following line should work
+The following two examples should give you a valid connection (however, the '''port 3306''' must be open to connect to ihp-pc45 on your side):
+
+The first option is through the mysql-client:
 
 {{{
@@ -16 +18 @@
 
 If you access the database from outside of ETH, it is wise to '''enable compression''' with the -C option. Inside ETH (in particular on ihp-pc45), enabling -C is certainly a performance drawback and should be avoided.
+
+The second option is through a FACT++ tool:
+
+{{{
+rootifysql --uri fact:password@ihp-pc45.ethz.ch/factdata
+}}}
+
+It is wise to put the credentials into a configuration file (its default name is '''rootifysql.rc''') and make it readable only for you ("{{{chmod go-r rootifysql.rc}}}) to avoid that the credentials are visible in the processlist (top, htop, ps aux, etc.). The shortest configuration file would look like this:
+
+{{{
+uri=fact:password@ihp-pc45.ethz.ch/factdata
+}}}
 
 Note that the mysql client libraries at ISDC are too old and do not allow for encrypted connections. Thus no connection from ISDC is possible without tunnel. How to tunnel your connection is explained in the following. Note that it requires an account on ihp-pc45 (which I think should not be generally available). Thus this is mainly meant as a solution for automatic processes running at ISDC, for example, to update the database.