Mercurial > noffle
annotate debian/templates @ 390:2ad4c1c97734 noffle
[svn] * src/client.c: Return correct status from Client_postArt() and add
function comment detailing what return code should be, because it's
not obvious that the return code should report success when the
posting failed for reasons other than connection problems. This should fix
problem with failing posting stopping fetches. Thanks to Dan Jacobson
for spotting this.
* src/client.c: Fix problemette with filter discards not updating remote
group article count and so the overview being refetched until
and article appears that doesn't fall foul of the filter and thus does
update the remove group 'next article' marker. Thanks to Dan Jacobson
for spotting this.
* src/content.c: Don't be fooled into thinking a filename starting ".."
is just "..".
* src/outgoing.c: Don't assume "." and ".." are the first files returned
from readdir(). Thanks to Andreas Happe for spotting this.
* src/noffle.c: Update online help to include 'm' group posting status.
* src/server.c: Move incorrect updating of server.grp in doGrp() which was
causing doGrp() to not retrieve remote article details when in online
mode. Thanks to Miernik and Andreas Happe for reporting the problem.
| author | bears |
|---|---|
| date | Thu, 22 May 2003 10:04:38 +0100 |
| parents | 89143e773bc6 |
| children | c9ff77f643a2 |
| rev | line source |
|---|---|
| 301 | 1 Template: noffle/debconf |
| 2 Type: boolean | |
|
380
89143e773bc6
[svn] set default value for debconf'iguration to false
godisch
parents:
351
diff
changeset
|
3 Default: false |
| 338 | 4 _Description: Manage noffle configuration using debconf? |
| 5 I'm going to overwrite /etc/news/noffle.conf and /etc/default/noffle with | |
| 6 some defaults and your following answers, and will update /etc/inetd.conf | |
| 351 | 7 if you agree. |
| 301 | 8 |
| 9 Template: noffle/port | |
| 10 Type: string | |
| 338 | 11 _Default: 119 |
| 12 _Description: Please choose the port number noffle runs on: | |
| 13 The default port number for NNTP is 119 (nntp). However, perhaps you want | |
| 14 to run noffle alongside a normal NNTP server; in that case, choose another | |
| 15 number (above 1024, I recommend 10119), and configure your news reader also | |
| 16 to use that port number. | |
| 301 | 17 |
| 18 Template: noffle/server | |
| 19 Type: string | |
| 338 | 20 _Default: news |
| 21 _Description: Which parent NNTP server do you want to use? | |
| 22 Noffle expects to obtain its news from another NNTP server. Enter the name | |
| 23 of that server here. If the server uses a non-standard port number for the | |
| 24 NNTP connection, please fill that in here as 'servername:portnumber'. | |
| 301 | 25 |
| 26 Template: noffle/username | |
| 27 Type: string | |
| 338 | 28 _Description: What is your username when accessing your parent NNTP server? |
| 29 If you need to authenticate you may fill in your username on your parent | |
| 30 NNTP server; if not, just leave this field blank. | |
| 301 | 31 . |
| 32 This is not the preferred way of authentication, since your password will | |
| 338 | 33 be transmitted in clear text, see README.Debian for more details. |
| 301 | 34 |
| 35 Template: noffle/password | |
| 36 Type: password | |
| 338 | 37 _Description: What is your password when accessing your parent NNTP server? |
| 38 If you need to authenticate you may fill in your password on your parent | |
| 39 NNTP server; if not, just leave this field blank. Warning: This password | |
| 40 will be saved in plaintext in /etc/news/noffle.conf and in the debconf | |
| 41 database! | |
| 301 | 42 . |
| 43 This is not the preferred way of authentication, since your password will | |
| 338 | 44 be transmitted in clear text, see README.Debian for more details. |
| 301 | 45 |
| 46 Template: noffle/fetchmode | |
| 47 Type: select | |
| 338 | 48 _Choices: ppp, cron |
| 49 _Description: How is noffle supposed to fetch the articles? | |
| 50 If this is a dialup system, then noffle can be configured to fetch articles | |
| 51 when the PPP connection comes online. This is done via scripts in | |
| 52 /etc/ppp/ip-up.d/ and /etc/ppp/ip-down.d/. If you have a permanent | |
| 53 connection, noffle will assume it can always access the NNTP server and a | |
| 54 cron job will do. | |
| 301 | 55 |
| 56 Template: noffle/maxfetch | |
| 57 Type: string | |
| 338 | 58 _Default: 300 |
| 59 _Description: Fetch how many articles by default? | |
| 60 When noffle fetches articles, it will never fetch more than this amount; if | |
| 61 there are more, the oldest are discarded. | |
| 301 | 62 |
| 63 Template: noffle/default-expire | |
| 64 Type: string | |
| 338 | 65 _Default: 14 |
| 66 _Description: What should the default expire time (in days) be? | |
| 67 Noffle is configured to purge the local cache of articles older than a | |
| 68 certain limit. This parameter configures the minimum age of articles to | |
| 69 expire; this can be fine-tuned in /etc/news/noffle.conf if necessary. | |
| 301 | 70 Enter '0' to disable it. |