PrevFast BackwardFast ForwardNext

Chapter 21. Server Run-time Environment

Table of Contents
21.1. The enterprisedb User Account
21.2. Creating a Database Cluster
21.3. Starting the Database Server
21.3.1. Server Start-up Failures
21.3.2. Client Connection Problems
21.4. Run-time Configuration
21.4.1. File Locations
21.4.2. Connections and Authentication
21.4.3. Resource Consumption
21.4.4. Write Ahead Log
21.4.5. Query Planning
21.4.6. Error Reporting and Logging
21.4.7. Runtime Statistics
21.4.8. Client Connection Defaults
21.4.9. Lock Management
21.4.10. Preset Options
21.4.11. Short Options
21.5. Managing Kernel Resources
21.5.1. Shared Memory and Semaphores
21.5.2. Resource Limits
21.5.3. Linux Memory Overcommit
21.6. Shutting Down the Server
21.7. Secure TCP/IP Connections with SSH Tunnels

This chapter discusses how to set up and run the database server and the interactions with the operating system.

21.1. The enterprisedb User Account

As with any other server daemon that is connected to outside world, it is advisable to run EnterpriseDB under a separate user account. This user account should only own the data that is managed by the server, and should not be shared with other daemons. (For example, using the user nobody is a bad idea.) It is not advisable to install executables owned by this user because compromised systems could then modify their own binaries.

To add a Unix user account to your system, look for a command useradd or adduser. The user name enterprisedb is often used but is by no means required.

Note: The installers shipping with EnterpriseDB automatically create this account on your behalf if it does not already exist.

PrevHomeNext
Database Server AdministrationUpCreating a Database Cluster