Changes between Version 3 and Version 4 of DatabaseBasedAnalysis/Connection

Timestamp:

08/04/18 18:15:14 (6 years ago)

Author:

tbretz

Comment:

--

DatabaseBasedAnalysis/Connection

@@ -5 +5 @@
 For details on how to use these credentials see the man page of the mysql-client '''mysql''' ("{{{man mysql}}}"), the help page of the FACT++ tool '''rootifysql''' ("{{{rootifysql --help}}}") or the documentation of the tool of your choice.
 
-== User ==
+A connection from everywhere is allowed, if the connection is '''encrypted'''. Connections from ihp-pc45 might be unencrypted.
 
-The user 'fact' is allowed to connect from everywhere if an encrypted connection is used. Usually, all reasonably recent mysql clients are using encrypted connections. So in most cases, a simple should be enough
+For the mysql client the following line should work
 
-{{{> mysql -C -h ihp-pc45.ethz.ch -u fact -p factdata}}}
+{{{
+mysql -C -h ihp-pc45.ethz.ch -u fact -p factdata
+}}}
 
 To enforce encryption, --ssl (oder clients) or --ssl-mode=REQUIRED can be used. If you have problems with the connection, you can also try --protocol=TCP.
 
-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.
+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.
 
 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.