Domino 控制檯命令大全

Lotus Domino Administration in a Nutshell By Greg Neilson
1st Edition August 2000 1-56592-717-6, Order Number: 7176 384 pages, $24.95

Chapter 13
Domino Server Tasks and Console Commands
In this chapter, I discuss how to specify which component tasks Domino loads at startup and how to configure Domino to run scheduled maintenance tasks. This type of configuration is usually done once as the server is commissioned, with occasional changes as needed.

There is also a set of commands that you can issue at the Domino server console to dynamically control the operation of the server. These commands are typically used to diagnose and resolve issues with Domino operations, make dynamic configuration changes to the Domino server, or to override scheduled operations and make things such as mail routing or database replication happen immediately.

Domino Server Tasks
A few lines in NOTES.INI define which server tasks are started when the server starts up, and also which scheduled tasks are to run at various times during the day.

The ServerTasks= line lists the tasks to start as the server starts up. The scheduled tasks are listed in the ServerTasksAt0= to ServerTasksAt23= lines. These specifications use the 24-hour clock, where 0 is midnight and 23 is 11:00 P.M.

Another option for scheduling tasks is the Program document in the Domino Directory. The Program document is described in Chapter 2, Domino Directories.

By default, the following tasks are configured to start, depending on how the server has been configured:

When the Quick and Easy Configuration setup option is selected, the tasks set to start at startup are Router, Replica, Update, AMgr, AdminP, CalConn, Event, Sched , Stats, and Maps. Then other tasks are added depending on which other client audience options are selected:

Web Browsers adds HTTP and DIIOP

Internet Mail Packages adds IMAP and POP3

News Readers adds NNTP

Enterprise Connection Services adds DECs

When the Advanced Configuration setup option is selected, the tasks set to start at startup are AdminP, AMgr, Update, Replica, Router, and Maps. Other tasks, such as CalConn, Event, Sched, and Stat, are optionally added if selected. Other tasks are added if they are selected by name. These are:
HTTP, DIIOP
IMAP, POP3
LDAP
NNTP
DECS

When the server has been upgraded from 4.x, you are not required to run the setup application after the code has been installed. This means that the original list of startup tasks is retained. Because the Reports task no longer exists in R5 and has been replaced by the Collect task, you must remove it. You also must remove the SMTPMTA statement, since this function has been added to the Router process.

Then, for the scheduled tasks in NOTES.INI, these entries are added as part of the original installation:

ServerTasksAt1=Catalog,Design
ServerTasksAt2=UpdAll,Object Collect mailobj.nsf
ServerTasksAt3=Object Info -Full
ServerTasksAt5=Statlog

You should also be aware that after you reinstall or upgrade your Domino server code, these entries are usually added again to NOTES.INI, if they had been removed.

Here is a list of all of the Domino server tasks, their functions, and the specific console commands they accept:

AdminP
The Administration Process automates many administration tasks. This task has the following commands available to modify its behavior while it is running:

tell adminp process all
Instructs the admin process to process all new and modified immediate/interval/daily/delayed requests.

tell adminp process daily
Instructs the admin process to process all new and modified daily requests.

tell adminp process delayed
Instructs the admin process to process all new and modified delayed requests.

tell adminp process interval
Instructs the admin process to process all immediate and interval requests.

tell adminp process new
Instructs the admin process to process all new requests.

tell adminp process people
Instructs the admin process to process all new and modified requests to update Person records within the Domino Directory.

tell adminp process time
Instructs the admin process to process all new and modified requests to delete mail files that become unlinked.

tell adminp show databases
Lists the databases that an administration server manages, and also lists databases that do not have an administration server configured.

AMgr
The Agent Manager runs scheduled and triggered agents in Domino databases. This task has the following commands available to modify its behavior while it is running:

tell amgr pause
Pauses the agent manager service, so no new agents can be scheduled for execution on the server.

tell amgr resume
Resumes the agent manager service, so new agents can be scheduled for execution on the server.

tell amgr schedule
Displays the scheduled agents that are to run today, and also the database in which they reside.

tell amgr status
Displays the status of the agent manager, and also configuration information of the agent manager from the server document in the Domino Directory.

Billing
Collects the configured usage information for billing.

Calconn (Calendar Connector)
Used to request free/busy time information for users whose mail databases reside on other servers.

Catalog
Maintains the Domain Catalog, which helps users to find and locate Domino databases and files of interest to them within the Domino domain.

Chronos
Performs updates of database full text indexes for databases that are configured to be updated hourly or daily. This task is autostarted by Domino and does not need to be added to NOTES.INI in order to run. You can cause this task to run immediately by issuing the commands load chronos daily or load chronos hourly.

Cladmin (Cluster Administration Process)
Ensures correct operation of the Domino application-level cluster.

Cldbdir (Cluster Database Directory Manager)
Maintains the cluster database directory.

Clrepl (Cluster Replicator)
Replicates between servers in a cluster in real time. Cluster replication is event-driven, whereas standard replication is schedule-driven. This task has the following commands available to modify its behavior while it is running:

tell clrepl log
Instructs the cluster replication tasks to immediately log information into the server log database, rather than wait for the defined log interval. Use this command when cluster replication is encountering problems--you can view the log entries for the errors and ensure that the problem is resolved before the next cluster replication attempt.

Collect
Collects server activity statistics from one or more servers. This task has the following command available to modify its behavior while it is running:

tell collector collect
Runs the Domino server statistic collection on every server specified and creates statistic reports.

Compact (Database Compaction)
Reorganizes the disk usage by each database in order to free up unused space. The Compact task can be invoked with the following commands (the various options can be combined as needed):

load compact [database]
Compacts the database or specified subdirectory.

load compact [database] -S X
Compacts databases with greater than X % free space.

load compact [database] -D
Compacts databases and deletes any built view indexes.

load compact [database] -R
Compacts databases and changes the ODS version to R4 from R5. Used when backing out of an upgrade from R4 to R5.

load compact [database] -M
For R4 databases, sets a maximum size of 4GB and compacts the database.

load compact [database] -b
Compacts databases in place. Can be used only if the database internal format is not being changed due to a change in one if the advanced database properties. It recovers unused space within the database, but does not reduce the file size of the database.

load compact [database] -B
Compacts databases in place. It recovers unused space within the database, and does reduce the file size of the database.

load compact [database] -c
Uses copy-style compaction of the database, rather than in-place compaction.

load compact [database] -L
When using copy-style compaction, allows access to the database while the compaction is in process. Compaction ends for the database if a user accesses the database.

load compact [database] -i
When using copy-style compaction, ignores any errors that occur during compaction.

load compact [database] -f
Compacts the database and changes the format of the database to disable support for document table bitmap optimization.

load compact [database] -F
Compacts the database and changes the format of the database to enable support for document table bitmap optimization.

load compact [database] -H
Compacts the database and changes the format of the database to enable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae.

load compact [database] -h
Compacts the database and changes the format of the database to disable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae.

load compact [database] -T
Compacts the database and changes the format of the database to enable transactional logging.

load compact [database] -t
Compacts the database and changes the format of the database to disable transactional logging.

load compact [database] -U
Compacts the database and changes the format of the database to maintain unread marks.

load compact [database] -u
Compacts the database and changes the format of the database to disable maintaining unread marks.Displays the scheduled agents that are to run today, and also the database in which they reside.

tell amgr status
Displays the status of the agent manager, and also configuration information of the agent manager from the server document in the Domino Directory.

Billing
Collects the configured usage information for billing.

Calconn (Calendar Connector)
Used to request free/busy time information for users whose mail databases reside on other servers.

Catalog
Maintains the Domain Catalog, which helps users to find and locate Domino databases and files of interest to them within the Domino domain.

Chronos
Performs updates of database full text indexes for databases that are configured to be updated hourly or daily. This task is autostarted by Domino and does not need to be added to NOTES.INI in order to run. You can cause this task to run immediately by issuing the commands load chronos daily or load chronos hourly.

Cladmin (Cluster Administration Process)
Ensures correct operation of the Domino application-level cluster.

Cldbdir (Cluster Database Directory Manager)
Maintains the cluster database directory.

Clrepl (Cluster Replicator)
Replicates between servers in a cluster in real time. Cluster replication is event-driven, whereas standard replication is schedule-driven. This task has the following commands available to modify its behavior while it is running:

tell clrepl log
Instructs the cluster replication tasks to immediately log information into the server log database, rather than wait for the defined log interval. Use this command when cluster replication is encountering problems--you can view the log entries for the errors and ensure that the problem is resolved before the next cluster replication attempt.

Collect
Collects server activity statistics from one or more servers. This task has the following command available to modify its behavior while it is running:

tell collector collect
Runs the Domino server statistic collection on every server specified and creates statistic reports.

Compact (Database Compaction)
Reorganizes the disk usage by each database in order to free up unused space. The Compact task can be invoked with the following commands (the various options can be combined as needed):

load compact [database]
Compacts the database or specified subdirectory.

load compact [database] -S X
Compacts databases with greater than X % free space.

load compact [database] -D
Compacts databases and deletes any built view indexes.

load compact [database] -R
Compacts databases and changes the ODS version to R4 from R5. Used when backing out of an upgrade from R4 to R5.

load compact [database] -M
For R4 databases, sets a maximum size of 4GB and compacts the database.

load compact [database] -b
Compacts databases in place. Can be used only if the database internal format is not being changed due to a change in one if the advanced database properties. It recovers unused space within the database, but does not reduce the file size of the database.

load compact [database] -B
Compacts databases in place. It recovers unused space within the database, and does reduce the file size of the database.

load compact [database] -c
Uses copy-style compaction of the database, rather than in-place compaction.

load compact [database] -L
When using copy-style compaction, allows access to the database while the compaction is in process. Compaction ends for the database if a user accesses the database.

load compact [database] -i
When using copy-style compaction, ignores any errors that occur during compaction.

load compact [database] -f
Compacts the database and changes the format of the database to disable support for document table bitmap optimization.

load compact [database] -F
Compacts the database and changes the format of the database to enable support for document table bitmap optimization.

load compact [database] -H
Compacts the database and changes the format of the database to enable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae.

load compact [database] -h
Compacts the database and changes the format of the database to disable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae.

load compact [database] -T
Compacts the database and changes the format of the database to enable transactional logging.

load compact [database] -t
Compacts the database and changes the format of the database to disable transactional logging.

load compact [database] -U
Compacts the database and changes the format of the database to maintain unread marks.

load compact [database] -u
Compacts the database and changes the format of the database to disable maintaining unread marks.
 
load compact [database] -A
Doesn't compact the database; archives documents to another database, and then deletes those documents from this database if archiving is set up for the database.

load compact [database] -a
If archiving is set up for the database, archives documents to another database and then deletes these documents from this database and compacts the database.

Convert
Used to update the mail databases to a new mail template design, typically used when upgrading the server to from R4 to R5. The Convert task can be invoked with the following commands:

load convert [-r] mailfilepath currenttemplatename newtemplatename
Converts the mail databases in the given mailfilepath from the currenttemplatename (* can be used to match all existing templates) to the newtemplatename. The new mail template for R5 is called MAIL50.NTF. The -r option is used to recursively process subdirectories below the given mailfilepath.

load convert -l mailfilelist
Produces a list of primary mail databases (but not replicas) on the server and writes the list to the file specified in mailfilelist. This option is used to produce a list of mail database files, which would be used with the -f option as shown in the next entry.

load convert -f mailfilelist currenttemplatename newtemplatename
Updates the mail databases listed in the mailfilelist from the currenttemplatename (* can be used to match all previous templates) to the newtemplatename. The new template in R5 is called MAIL50.NTF.

load convert -m mailfilepath
Changes the mail databases specified within the mailfilepath to able be used for IMAP mail access.

DECS (Domino Enterprise Connection Services)
Enables hot linking between documents within a Domino database and backend data sources such as DB2 or Oracle.

Design
Updates database designs from their template.

DIIOP
An object request broker; allows browser clients running Java applets to access backend Notes database objects via the IIOP protocol. This task has the following commands available to modify its behavior while it is running:

tell diiop show users
Shows all active users connected to the server by DIIOP.

tell diiop drop all
Drops all user connections using DIIOP immediately.

Dircat
Maintains small copies of the Domino Directory called the Directory Catalog, which can be used for user lookup for mobile/laptop users. This task is usually not started via an entry in NOTES.INI; when you enable a schedule on the Directory Cataloger tab in the Server Document this task is launched automatically.

Event (Event Monitor)
Tracks of specific events that have occurred on the Domino server

Fixup
Fixes suspected corrupt Domino databases. These options can be combined as needed:

load fixup [database] -F
When fixup runs against multiple databases, by default it checks only documents with the last modified date since its last run. This parameter then forces the fixup task to check all documents in all databases being checked.

load fixup [database] -i
Checks only new documents in the database since the last run of fixup.

load fixup [database] -J
Runs fixup against databases that have transaction logging enabled. If this parameter isn't used, fixup doesn't check these databases.

load fixup -L
When used without specifying the database to check, logs every database suspected of being corrupted. The default is to log only when a database problem is found and needs to be corrected.

load fixup [database] -N
Changes the way that fixup operates when a corrupted document within a database is encountered. When this parameter is specified, any corrupted documents found are not deleted. A typical use of this is to allow documents to be copied to another database before fixup deletes them in an effort to retrieve documents from a corrupted database.

load fixup [database] -Q
Instructs fixup to be less thorough in its checking for corrupted documents in the database.

load fixup [database] -U
Changes unread document lists to the older R4 format. (Lotus recommends that you do this only when requested by Lotus Support.)

load fixup [database] -V
Specifies to not check views for corruption.

HTTP (Domino web server)
Serves regular HTML/CGI and converts Domino elements into HTML/Java applets as required. This task has the following commands available to modify its behavior while it is running:

tell http restart
Refreshes the configuration for the HTTP task without having to unload and reload the task into the server memory.

tell http show file access
Shows filesystem access on the server for HTTP clients.

tell http show security
Displays SSL configuration information for the web server.

tell http show users
Shows the current list of session-based users that are connected and authenticated to Domino.

tell http show virtual servers
Displays the configured virtual web servers defined on the Domino server.
 
ICM (Internet Cluster Manager)
Manages access to clustered servers for HTTP (web) clients.

IMAP
Facilitates access to Domino mail databases by IMAP clients.

LDAP
Facilitates access to the Domino Directory by LDAP clients. This task has the following commands available to modify its behavior while it is running:

tell ldap reloadschema
Updates the schema for LDAP to reflect customizations made to the Domino Directory.

tell ldap exportschema
Creates or updates the schema database (SCHEMA50.NSF) to reflect schema changes in the Domino Directory.

Maps
Extracts information from Connection documents to produce the graphical replication and routing information in Domino Administrator.

MTC (Message Tracking Collector)
Monitors the work of the Router process (which delivers mail in Domino) and keeps records as required as to what mail was sent to whom. This allows users and administrators to query mail status. This task does not need to be explicitly started; if mail tracking is enabled on the server by a Configuration document, then Domino will start this task automatically as the Router task is started.

tell mtc process
Collects information now for message tracking, rather than waiting for the message tracking interval.

tell mtc interval value
Changes the collection interval used for message tracking information by the MTC task.

tell mtc compact
Compacts the message tracking store database now.

tell mtc reindex
Reindexes the message tracking store database now.

tell mtc purge value
Purges collected message tracking information older than value days from the message tracking database now.

NNTP
Enables the Domino server to be used as a newsgroup server. This task has the following commands available to modify its behavior while it is running:

tell nntp newgroup newsgroupname
Creates a new newsgroup called newsgroupname.

tell nntp newgroup delete groupname1, groupname2
Deletes the specified newsgroups.

tell nntp newgroup newsgroupname pathname
Tells the NNTP task to add a new newsgroup to its cache using the specified database.

tell nntp print cache list
Displays the current newsgroups and their corresponding databases.

tell nntp print config
Shows the configuration information for the NNTP server.

tell nntp reset servername
Resets the newsfeed from the specified server, so the next newsfeed will be considered an initial newsfeed.

tell nntp show config
Shows the configuration information for the NNTP server.

tell nttp show groups
Shows the currently configured newsgroups on the server, and the path of each relative to the data directory on the server.

Object (Object Store Manager)
Works with single-object store mail databases, if enabled. The Object task can be invoked as follows:

load object create sharedmaildb.nsf
Creates a new shared mail database with the name sharedmaildb.nsf.

load object link usermaildb.nsf sharedmaildb.nsf
Links messages already present within sharedmaildb.nsf into the shared mail database.

load object link -nocompact usermaildb.nsf sharedmaildb.nsf
Links messages already present within sharedmaildb.nsf into the shared mail database. The -nocompact option means that usermaildb.nsf is not compacted (which reclaims unused space in databases) even if there are more than five messages linked into sharedmaildb.nsf.

load object link -relink usermaildb.nsf sharedmaildb.nsf
Links a user's mail database to a different sharedmaildb.nsf.

load object unlink usermaildb.nsf
Unlinks messages for the given usermaildb.nsf.

load object unlink sharedmaildb.nsf
Unlinks messages for the given sharedmaildb.nsf.

load object set -never usermaildb.nsf
Sets usermaildb.nsf to never use shared mail.

load object reset -never usermaildb.nsf
Removes the setting to never use shared mail for usernmildb.nsf.

load object set -always usermaildb.nsf sharedmaildb.nsf
Ensures all replicas of the usermaildb.nsf use the shared mail database sharedmaildb.nsf.

load object reset -always usermaildb.nsf
Removes the setting that makes sure all replicas of usermaildb.nsf use the shared mail database.

load object collect -nodelete
Checks which old messages are ready to be deleted, but does not actually delete them.

load object collect usermaildb.nsf
Deletes obsolete messages from the usermaildb.nsf.

load object collect sharedmaildb.nsf
Deletes obsolete messages from the sharedmaildb.nsf.

load object collect -force sharedmaildb.nsf
The -force option is used after a user mail database has been deleted, and you wish to reclaim the space used for linked messages in sharedmaildb.nsf that were referred to only from that user mail database.

load object info usermaildb.nsf
Checks whether the usermaildb.nsf contains any messages that use a shared mail database.
 
發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章