Section: User Commands (1)
Return to Main Contents
ezmlm-test - test ezmlm programs
is run from the ezmlm build directory. It will test most of the
functions of most of the programs in ezmlm-idx. The program prints
status and error messages to stdout. It requires that qmail runs on the
host and that mail delivery to a local user functions. The invoking user
should have read and execute permission to the files in the build
directory, and write permission in the current directory.
For testing with an SQL database, a number of switches allow overriding
the default connection information.
creates a test list in the directory ``__TSTDIR'' (in the current
directory). This directory and ``dot.qmail-__tstlist*'' will be
overwritten/removed by the program. In addition, the file
``__TSTDIR_err'' is created. In cases of error, it often contains the
error message from the failing program.
should complete without error.
As many invocations of the programs test several functions it is not easy
to determine what went wrong if
fails. Usually, ``__TSTDIR__err'' gives some leads, but then debugging
of the particular program is required. Usually, this involves recreating
the failing circumstances, including environment variables.
- -d sqldatabase
If SQL support is tested, use
as the database, overriding the default ``ezmlm''. See
- -h host
Connect to an SQL server on
if an SQL database is used (see
Default is empty, which for most database managers defaults to
localhost/unix socket. To specify a non-default port,
add ``:port'' to the host name.
- -p sqlpassword
Test with SQL support, and use
as the connection password. By default, local databases, rather than an
SQL database are used for testing. To use the SQL database with an
empty password, specify
- -s subdb
plugin for the subscriber databases.
- -t sqltable
as the table root name for the SQL database tables, if an SQL database
is used (see
Default is ``list''.
- -u sqluser
to the SQL server, if an SQL database is used (see
Default is ``eztest''.
On some systems, some of the tests give a broken pipe error. This is because
code needs to be added to the make_message function to capture error messages.
These errors can be safely ignored for now.
- SEE ALSO
This document was created by
using the manual pages.
Time: 18:00:51 GMT, June 16, 2008