]>
Commit | Line | Data |
---|---|---|
4a9bd1fd | 1 | --- newscache-1.1.92.orig/doc/NewsCache.info |
2 | +++ newscache-1.1.92/doc/NewsCache.info | |
3 | @@ -1,5 +1,5 @@ | |
4 | -This is Info file NewsCache.info, produced by Makeinfo version 1.68 | |
5 | -from the input file NewsCache.texinfo. | |
6 | +This is NewsCache.info, produced by makeinfo version 4.1 from | |
7 | +NewsCache.texinfo. | |
8 | ||
9 | This is the NewsCache Reference Manual. | |
10 | ||
11 | @@ -109,7 +109,7 @@ | |
12 | Some news readers mark deleted articles as read. However, if the | |
13 | article is reinstated on the news server, the article is still marked | |
14 | as read and the user will never see this article as unread. According | |
15 | -to RFC977, (Network News Transfer Protocol) (http://info.internet.isi.edu/in-notes/rfc/files/rfc977.txt) it is allowed that deleted articles | |
16 | +to (Network News Transfer Protocol) it is allowed that deleted articles | |
17 | are reinstated. This is also documented in the new NNTP-draft which | |
18 | should be published as RFC within the next months. | |
19 | ||
20 | @@ -204,8 +204,8 @@ | |
21 | Admin you@your.provider | |
22 | ||
23 | Timeouts for the retrieval of the active database and the description | |
24 | -(*In version 0.99.13, the retrieval of the newsgroup descriptions is | |
25 | -not implemented*) of the newsgroups are set with the `Timeouts' command | |
26 | +(_In version 0.99.13, the retrieval of the newsgroup descriptions is | |
27 | +not implemented_) of the newsgroups are set with the `Timeouts' command | |
28 | (The values are given in seconds). The values indicate the time, when | |
29 | NewsCache reloads the active database or the description of the | |
30 | newsgroups. While the active database changes rather frequently, the | |
31 | @@ -231,11 +231,11 @@ | |
32 | crond. `NewsCacheClean' removes newsgroups until the used diskspace is | |
33 | below `SpoolSize'. | |
34 | ||
35 | - *Before starting NewsCache, check that this directory exists and | |
36 | + _Before starting NewsCache, check that this directory exists and | |
37 | that NewsCache has read and write permissions. Additionally, this | |
38 | directory must be on a local partition! NewsCache uses file locking and | |
39 | does not make use of lockd. Mounting this directory via NFS would | |
40 | -decrease performance, so it does not make sense anyway.* | |
41 | +decrease performance, so it does not make sense anyway._ | |
42 | ||
43 | SpoolDirectory /lhome/newscache/NSpool | |
44 | SpoolSize 100000 | |
45 | @@ -249,8 +249,8 @@ | |
46 | ||
47 | If you are using log files you have to set the log directory using | |
48 | the `LogDirectory' command. If you are using syslogd, this statement | |
49 | -has no effect. *Before starting NewsCache, check that this directory | |
50 | -exists and that NewsCache has read and write permissions.* | |
51 | +has no effect. _Before starting NewsCache, check that this directory | |
52 | +exists and that NewsCache has read and write permissions._ | |
53 | ||
54 | LogDirectory /lhome/newscache/log | |
55 | ||
56 | @@ -259,8 +259,8 @@ | |
57 | both. NewsCache uses the same log format as INN and some additional log | |
58 | entries. If you want to log only INN style log messages, add the | |
59 | `strict-inn' option. This will be only useful if you use some statistic | |
60 | -tools for INN that get confused with those extra messages. *In version | |
61 | -0.99.13 `strict-inn' is only supported on the LOG_NOTICE level.* | |
62 | +tools for INN that get confused with those extra messages. _In version | |
63 | +0.99.13 `strict-inn' is only supported on the LOG_NOTICE level._ | |
64 | ||
65 | LogStyle ip-address strict-inn | |
66 | ||
67 | @@ -339,7 +339,7 @@ | |
68 | contact the upstream news server; `semioffline'--contact the | |
69 | upstream news server whenever necessary, except for retrieving the | |
70 | list of newsgroups; `not-setpostflag', `setpostflag'; | |
71 | - `not-cached', `cached'. | |
72 | + `not-cached', `cached'; `dontgenmsgid'; `lowbandwidth'. | |
73 | ||
74 | `Commands' | |
75 | This option indicates which commands are (or are not) supported by | |
76 | @@ -419,11 +419,11 @@ | |
77 | a good connection to our local news server. In fact they are located on | |
78 | the same machine. | |
79 | ||
80 | - *Whether the cached/not-cached flag is supported depends on your | |
81 | + _Whether the cached/not-cached flag is supported depends on your | |
82 | installation. If you configured NewsCache at compile time with the | |
83 | `--enable-notcached' flag this flag is supported, otherwise not. This | |
84 | is disabled by default due to problems of gcc-2.7.2. If you are using | |
85 | -egcs or gcc-2.8.1, you can turn on this flag safely.* | |
86 | +egcs or gcc-2.8.1, you can turn on this flag safely._ | |
87 | ||
88 | Replacing a Leaf Node News Server | |
89 | ================================= | |
90 | @@ -564,7 +564,7 @@ | |
91 | active database will be requested twice from news.tuwien.ac.at. In our | |
92 | case for all newsgroups, with all the at.tuwien.* groups eliminated and | |
93 | once for all the at.tuwien.* groups. If the news server does not support | |
94 | -the `list active [wildmat]' command, the *whole* active database will | |
95 | +the `list active [wildmat]' command, the _whole_ active database will | |
96 | be requested twice. While this does not matter for a news server with | |
97 | a good connection to the cache, you will think twice reconsider your | |
98 | choice if the connection is not that good. | |
99 | @@ -661,13 +661,13 @@ | |
100 | ************************** | |
101 | ||
102 | Where can I get NewsCache? | |
103 | - You can can get NewsCache from its | |
104 | - homepage (http://www.infosys.tuwien.ac.at/NewsCache/). | |
105 | + You can can get NewsCache from its homepage | |
106 | + (http://www.infosys.tuwien.ac.at/NewsCache/). | |
107 | ||
108 | What is the latest version of NewsCache? | |
109 | As of this writing the latest version is 0.99.13. The latest | |
110 | - version of NewsCache can always be found at its | |
111 | - homepage (http://www.infosys.tuwien.ac.at/NewsCache/). | |
112 | + version of NewsCache can always be found at its homepage | |
113 | + (http://www.infosys.tuwien.ac.at/NewsCache/). | |
114 | ||
115 | How does this compare to NNTPCACHE? | |
116 | NNTPCACHE is a cache server similar to NewsCache. Features of | |
117 | @@ -807,16 +807,16 @@ | |
118 | ||
119 | \1f | |
120 | Tag Table: | |
121 | -Node: Top\7f939 | |
122 | -Node: Introduction\7f1929 | |
123 | -Node: Compatibility\7f3686 | |
124 | -Node: General Options\7f5941 | |
125 | -Node: ServerList Option\7f12020 | |
126 | -Node: Access Control\7f24092 | |
127 | -Node: Statistics\7f24900 | |
128 | -Node: Bugs and Misfeatures\7f25318 | |
129 | -Node: FAQ\7f26509 | |
130 | -Node: Inside NewsCache\7f29572 | |
131 | -Node: Concept Index\7f30467 | |
132 | +Node: Top\7f913 | |
133 | +Node: Introduction\7f1903 | |
134 | +Node: Compatibility\7f3660 | |
135 | +Node: General Options\7f5846 | |
136 | +Node: ServerList Option\7f11925 | |
137 | +Node: Access Control\7f24029 | |
138 | +Node: Statistics\7f24837 | |
139 | +Node: Bugs and Misfeatures\7f25255 | |
140 | +Node: FAQ\7f26446 | |
141 | +Node: Inside NewsCache\7f29509 | |
142 | +Node: Concept Index\7f30404 | |
143 | \1f | |
144 | End Tag Table | |
145 | --- newscache-1.1.92.orig/doc/NewsCache.texinfo | |
146 | +++ newscache-1.1.92/doc/NewsCache.texinfo | |
147 | @@ -452,7 +452,7 @@ | |
148 | contact the upstream news server; @code{semioffline}---contact the | |
149 | upstream news server whenever necessary, except for retrieving the list | |
150 | of newsgroups; @code{not-setpostflag}, @code{setpostflag}; | |
151 | -@code{not-cached}, @code{cached}. | |
152 | +@code{not-cached}, @code{cached}; @code{dontgenmsgid}; @code{lowbandwidth}. | |
153 | @item Commands | |
154 | This option indicates which commands are (or are not) supported by the | |
155 | upstream news server. Some versions of the netscape collabra server do |