aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSergey Poznyakoff <gray@gnu.org.ua>2007-05-04 06:30:49 +0000
committerSergey Poznyakoff <gray@gnu.org.ua>2007-05-04 06:30:49 +0000
commit668377d11b47ce5b0b165dcca72bbff90a066f04 (patch)
tree013a3d0a29628ab0d5bf5e543eec320bdeecbe37 /doc
parent5663888746b3b5e15ab795a1e2bfaae7b2cf768a (diff)
downloadmailfromd-668377d11b47ce5b0b165dcca72bbff90a066f04.tar.gz
mailfromd-668377d11b47ce5b0b165dcca72bbff90a066f04.tar.bz2
Fixes
git-svn-id: file:///svnroot/mailfromd/trunk@1406 7a8a7f39-df28-0410-adc6-e0d955640f24
Diffstat (limited to 'doc')
-rw-r--r--doc/mailfromd.texi25
1 files changed, 13 insertions, 12 deletions
diff --git a/doc/mailfromd.texi b/doc/mailfromd.texi
index ffd1495c..553c3498 100644
--- a/doc/mailfromd.texi
+++ b/doc/mailfromd.texi
@@ -2321,11 +2321,11 @@ database is the prediction of @dfn{estimated time of sending},
i.e. the time when the user will be able to send mail if currently his
mail sending rate has exceeded the limit. This is done using
@option{--predict} option. The option takes an argument, specifying
-the mail sending rate limit, e.g.:
+the mail sending rate limit, e.g. (the second line is split for readability):
@smallexample
@group
-$ @kbd{mailfromd --list --format=rate --predict="180 per 1 minute"}
+$ @kbd{mailfromd --predict="180 per 1 minute"}
ed@@fae.net-21.10.1.2 Wed Sep 13 03:53:40 2006 0 1 N/A N/A; free to send
service@@19.netlay.com-69.44.129.19 Wed Sep 13 15:46:07 2006 7 2
0.286 0.0224; in 46 sec. on Wed Sep 13 15:49:00 2006
@@ -2333,7 +2333,8 @@ service@@19.netlay.com-69.44.129.19 Wed Sep 13 15:46:07 2006 7 2
@end smallexample
@noindent
-(the second line is split for readability)
+Notice, that there is no need to use @option{--list --format=rate}
+along with this option, although doing so is not an error.
@anchor{deleting from databases}
@xopindex{delete, introduced}
@@ -2371,15 +2372,15 @@ database.
@xopindex{compact, introduced}
This is done by running @kbd{mailfromd --compact} (and, optionally,
specifying the database to operate upon with @option{--format}
-option. Notice, that compacting a database needs roughly as
+option). Notice, that compacting a database needs roughly as
much disk space on the partition where the database resides as the
-database currently occupies. The simultaneous access prevention while
-compacting the database depends on the underlying @acronym{DBM}
-implementation. In general, it is locked, so the running copy
-of @command{mailfromd} is not able to write to it, but still can read
-the data from it. @FIXME{However, I need to verify the BerkeleyDB
-case, just to be sure. Although I have never experienced any problems
-while compacting BDBs.}
+database currently occupies. Database compaction runs in three phases.
+First, the database is scanned and all non-expired records are stored
+in the memory. Secondly, a temporary database is created in the state
+directory and all the cached entries are flushed into it. This
+database is named after the @acronym{PID} of the running
+@command{mailfromd} process. Finally, the temporary database is
+renamed to the source database.
@anchor{compact cronjob}
@xopindex{all, introduced}
@@ -9189,7 +9190,7 @@ are advised to use instead (@pxref{pragma pidfile}).
@item --predict=@var{rate-limit}
Used with @option{--list} enables printing of the estimated times of
sending along with the @samp{rate} database dump. Implies
-@option{--format=rate}. @xref{estimated time of sending}.
+@option{--list --format=rate}. @xref{estimated time of sending}.
@opsummary{relayed-domain-file}
@item --relayed-domain-file=@var{file}

Return to:

Send suggestions and report system problems to the System administrator.