[Top] [Prev] [Next] [Contents] [Index]

Messages and Modules Overview

As part of its ongoing activities, the X server issues messages about its operations. As the X server executes, each module (for example, the Configuration daemon) generates its own messages. The information reported includes successful completion of user requests, unsuccessful attempts to perform an action, or fatal errors that cause the X server to crash.

The modules that issue messages are not necessarily X server modules, although many of them are. A reporting module may also be a daemon, such as the Configuration daemon, or simply a discrete function of the X server.

The messages are stored in an internal buffer and forwarded to the Console Messages hide box. If there is an existing TELNET connection, the messages are sent there as well.

You can also configure the terminal to write messages to a log file. Console messages are the same as messages logged to a file, except that Console messages do not include a time stamp.

Many of the messages displayed in the Console are issued by the terminal as it boots, after the X server is executed. These messages show how the terminal reads its configuration file, keymap file, color definition file, and fonts. Other messages in the Console reflect ongoing operations, such as starting clients and loading fonts as clients request them.

Messages are listed by module and alphabetically within each module section. The text of each message is followed by a table listing the severity, the explanation, and the recommended user action, if any.

The first section of messages describes those that are common to many modules, followed by a separate section for each module that issues its own unique messages.

[Top] [Prev] [Next] [Contents] [Index]

Send comments, suggestions, or questions about this document to the NCD Technical Publications Department by Internet e-mail. Write to us at techpubs@ncd.com.
Copyright © 1997, NCD Inc. All rights reserved.