Dissertaç ˜ao de Mestrado Mestrado em Engenharia Informática Jo ...

More documents

Recommendations

Info

B. APPENDIX - EVALUATION B.5. Performance Validation File 2 # MAPNAME is the (otherwise freely chosen) map name that was used in # pg_hba.conf. IDENT-USERNAME is the detected user name of the # client. PG-USERNAME is the requested PostgreSQL user name. The # existence of a record specifies that IDENT-USERNAME may connect as # PG-USERNAME. Multiple maps may be specified in this file and used # by pg_hba.conf. # # This file is read on server startup and when the postmaster receives # a SIGHUP signal. If you edit the file on a running system, you have # to SIGHUP the postmaster for the changes to take effect. You can use # "pg_ctl reload" to do that. # Put your actual configuration here # ---------------------------------- # # No map names are defined in the default configuration. If all ident # user names and PostgreSQL user names are the same, you don’t need # this file. Instead, use the special map name "sameuser" in # pg_hba.conf. # MAPNAME IDENT-USERNAME PG-USERNAME B.5 Performance Validation File 2 # PostgreSQL Client Authentication Configuration File # =================================================== # # Refer to the "Client Authentication" section in the # PostgreSQL documentation for a complete description # of this file. A short synopsis follows. # # This file controls: which hosts are allowed to connect, how clients # are authenticated, which PostgreSQL user names they can use, which # databases they can access. Records take one of these forms: # # local DATABASE USER METHOD [OPTION] 140
B. APPENDIX - EVALUATION B.5. Performance Validation File 2 # host DATABASE USER CIDR-ADDRESS METHOD [OPTION] # hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION] # hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION] # # (The uppercase items must be replaced by actual values.) # # The first field is the connection type: "local" is a Unix-domain socket, # "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an # SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP # socket. # DATABASE can be "all", "sameuser", "samerole", a database name, or # a comma-separated list thereof. # # USER can be "all", a user name, a group name prefixed with "+", or # a comma-separated list thereof. In both the DATABASE and USER fields # you can also write a file name prefixed with "@" to include names from # a separate file. # # CIDR-ADDRESS specifies the set of hosts the record matches. # It is made up of an IP address and a CIDR mask that is an integer # (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies # the number of significant bits in the mask. Alternatively, you can write # an IP address and netmask in separate columns to specify the set of # hosts. # METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi", # "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords # in clear text; "md5" is preferred since it sends encrypted # passwords. # OPTION is the ident map or the name of the PAM service, depending # on METHOD. 141
Page 1:
Universidade Nova de Lisboa Faculda
Page 5:
To my family and friends, who suppo
Page 9:
Sumário Entre os sectores de tecno
Page 12 and 13:
CONTENTS 3.5 Modifying the Configur
Page 15:
List of Figures 2.1 Virtual applian
Page 19 and 20:
List of Listings 1.1 Apache configu
Page 21 and 22:
1 Introduction This dissertation pr
Page 23 and 24:
1. INTRODUCTION 1.2. Problem Descri
Page 25 and 26:
Page 27 and 28:
Page 29:
1. INTRODUCTION 1.5. Document Organ
Page 32 and 33:
2. STATE OF THE ART AND RELATED WOR
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 41 and 42:
3 An application reconfiguration fr
Page 43 and 44:
3. AN APPLICATION RECONFIGURATION F
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55:
Page 58 and 59:
4. AN IMPLEMENTATION 4.2. Parser Ge
Page 60 and 61:
4. AN IMPLEMENTATION 4.4. Data Stru
Page 62 and 63:
4. AN IMPLEMENTATION 4.4. Data Stru
Page 64 and 65:
4. AN IMPLEMENTATION 4.5. Original
Page 66 and 67:
4. AN IMPLEMENTATION 4.6. Generatio
Page 68 and 69:
4. AN IMPLEMENTATION 4.7. Generic t
Page 71 and 72:
5 Framework Evaluation Chapter 3 pr
Page 73 and 74:
5. FRAMEWORK EVALUATION 5.2. Operat
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
5. FRAMEWORK EVALUATION 5.3. Perfor
Page 85:
5. FRAMEWORK EVALUATION 5.3. Perfor
Page 88 and 89:
6. INTEGRATION WITH VIRTU 6.2. VIRT
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
6. INTEGRATION WITH VIRTU 6.4. SmAR
Page 96 and 97:
6. INTEGRATION WITH VIRTU 6.4. SmAR
Page 98 and 99:
6. INTEGRATION WITH VIRTU 6.5. Summ
Page 100 and 101:
7. CONCLUSION AND FUTURE WORK 7.1.
Page 103 and 104:
A.1 OGC sequence diagram A Appendix
Page 105 and 106:
B.1 MySQL Configuration file # # Th
Page 107 and 108:
B. APPENDIX - EVALUATION B.1. MySQL
Page 109 and 110: B. APPENDIX - EVALUATION B.2. Apach
Page 141 and 142: B. APPENDIX - EVALUATION B.3. Eclip
Page 159: B. APPENDIX - EVALUATION B.4. Perfo
Page 163 and 164: B. APPENDIX - EVALUATION B.6. Perfo
Page 179 and 180: Bibliography [Ama09] Amazon. Amazon
Page 181: BIBLIOGRAPHY [Sol09a] Evolve Space
show all

Dissertaç ˜ao de Mestrado Mestrado em Engenharia Informática Jo ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?