noffle-devel Mailing List for Noffle - news server
Brought to you by:
bears
Menu
▾
▴
noffle-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(17) |
Jul
(53) |
Aug
(14) |
Sep
(8) |
Oct
(16) |
Nov
(7) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(5) |
Feb
(4) |
Mar
(2) |
Apr
|
May
(22) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
(6) |
Nov
(23) |
Dec
(1) |
| 2002 |
Jan
(4) |
Feb
(1) |
Mar
(20) |
Apr
(7) |
May
(8) |
Jun
(9) |
Jul
(7) |
Aug
(4) |
Sep
|
Oct
(11) |
Nov
(2) |
Dec
(6) |
| 2003 |
Jan
(5) |
Feb
(11) |
Mar
(11) |
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
(4) |
| 2006 |
Jan
(3) |
Feb
(2) |
Mar
(4) |
Apr
(2) |
May
(9) |
Jun
(26) |
Jul
(11) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2006-07-12 19:28:35
|
Feature Requests item #1513395, was opened at 2006-06-27 15:48 Message generated for change (Comment added) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Priority: 5 Submitted By: Jan De Luyck (devilkin) Assigned to: Jim Hague (bears) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- >Comment By: Jim Hague (bears) Date: 2006-07-12 20:28 Message: Logged In: YES user_id=184 Patch now committed. I hope you'll forgive me; I changed message-id to messageid in your config name to be consistent with replace-messageid. ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2006-06-30 20:21 Message: Logged In: YES user_id=184 Semi-broken upstream NNTP servers. Oh, I love them, I do :-( Terrific idea, terrific patch. Simple, effective, neat. Thanks very much indeed; I will commit it the moment I can find the time. I guess I'd better let the world know I've moved the repository to Subversion too. :-) Glad you find the code easy to work with. Markus did an excellent job writing it in the first place, and I've tried to stick to the style he established. ---------------------------------------------------------------------- Comment By: Jan De Luyck (devilkin) Date: 2006-06-27 17:50 Message: Logged In: YES user_id=95363 Unfortunately, I have no clue. Sometimes, after posting the same message again and again for 10-ish times, the server will suddenly accept it. No idea why. The error returned by the astraweb server is: [ NOFFLE: POSTING OF ARTICLE FAILED ] [ The posting of your article failed. ] [ Reason of failure at remote server: ] [ 441 437 Rejected 679 000001 MsgIdMismatch ] [ Full article text has been appended. ] Newsgroups: be.test From: Jan De Luyck <jan...@kc...> Subject: test 2 User-Agent: slrn/0.9.8.1pl1 (Debian) Date: Tue, 27 Jun 2006 16:34:13 +0200 Message-ID: <200...@ru...cks- ass.org> Path: rutabaga.kicks-ass.org!not-for-mail Reply-To: Jan De Luyck <jan...@kc...> 1 2 hupsakdrie -- Linux rutabaga 2.6.17 #1 PREEMPT Mon Jun 19 08:02:42 CEST 2006 i686 GNU/Linux It's a poor workman who blames his tools. . ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2006-06-27 17:27 Message: Logged In: YES user_id=184 I understand the reason for what you want. Ideally I'd prefer to have Noffle generate a message ID acceptable to astraweb. Have you got any clues as to the problem with the Noffle message ID? I can't find any hints on the astraweb site, and I'm pretty sure the message IDs Noffle generates are 100% RFC compliant. If that does prove impossible, then it should be not too difficult to add an option for Noffle to strip out the message ID when forwarding the article upstream. ---------------------------------------------------------------------- Comment By: Jan De Luyck (devilkin) Date: 2006-06-27 17:22 Message: Logged In: YES user_id=95363 I did a bit of a dig through the Noffle sourcecode (it's damn clean code!) of which the Debian Sid packages are made, and this is the patch I came up with. It adds a new configuration option, add-message-id-if- missing (bool), through which you can control if a message id should be generated inside the message, or not. If you pick yes, Noffle works like it used to. If you choose no, it will not store a Message-ID: header in the text, but it will generate one to be able to store it in the outgoing queue. I've tested it locally, works like a charm ehre. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2006-06-27 16:28:15
|
Feature Requests item #1513395, was opened at 2006-06-27 16:48 Message generated for change (Settings changed) made by devilkin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: Jan De Luyck (devilkin) >Assigned to: Nobody/Anonymous (nobody) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2006-06-27 18:27 Message: Logged In: YES user_id=184 I understand the reason for what you want. Ideally I'd prefer to have Noffle generate a message ID acceptable to astraweb. Have you got any clues as to the problem with the Noffle message ID? I can't find any hints on the astraweb site, and I'm pretty sure the message IDs Noffle generates are 100% RFC compliant. If that does prove impossible, then it should be not too difficult to add an option for Noffle to strip out the message ID when forwarding the article upstream. ---------------------------------------------------------------------- Comment By: Jan De Luyck (devilkin) Date: 2006-06-27 18:22 Message: Logged In: YES user_id=95363 I did a bit of a dig through the Noffle sourcecode (it's damn clean code!) of which the Debian Sid packages are made, and this is the patch I came up with. It adds a new configuration option, add-message-id-if- missing (bool), through which you can control if a message id should be generated inside the message, or not. If you pick yes, Noffle works like it used to. If you choose no, it will not store a Message-ID: header in the text, but it will generate one to be able to store it in the outgoing queue. I've tested it locally, works like a charm ehre. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2006-06-27 16:27:14
|
Feature Requests item #1513395, was opened at 2006-06-27 15:48 Message generated for change (Comment added) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: Jan De Luyck (devilkin) >Assigned to: Jim Hague (bears) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- >Comment By: Jim Hague (bears) Date: 2006-06-27 17:27 Message: Logged In: YES user_id=184 I understand the reason for what you want. Ideally I'd prefer to have Noffle generate a message ID acceptable to astraweb. Have you got any clues as to the problem with the Noffle message ID? I can't find any hints on the astraweb site, and I'm pretty sure the message IDs Noffle generates are 100% RFC compliant. If that does prove impossible, then it should be not too difficult to add an option for Noffle to strip out the message ID when forwarding the article upstream. ---------------------------------------------------------------------- Comment By: Jan De Luyck (devilkin) Date: 2006-06-27 17:22 Message: Logged In: YES user_id=95363 I did a bit of a dig through the Noffle sourcecode (it's damn clean code!) of which the Debian Sid packages are made, and this is the patch I came up with. It adds a new configuration option, add-message-id-if- missing (bool), through which you can control if a message id should be generated inside the message, or not. If you pick yes, Noffle works like it used to. If you choose no, it will not store a Message-ID: header in the text, but it will generate one to be able to store it in the outgoing queue. I've tested it locally, works like a charm ehre. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2006-06-27 16:22:10
|
Feature Requests item #1513395, was opened at 2006-06-27 16:48 Message generated for change (Comment added) made by devilkin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: Jan De Luyck (devilkin) >Assigned to: Nobody/Anonymous (nobody) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- >Comment By: Jan De Luyck (devilkin) Date: 2006-06-27 18:22 Message: Logged In: YES user_id=95363 I did a bit of a dig through the Noffle sourcecode (it's damn clean code!) of which the Debian Sid packages are made, and this is the patch I came up with. It adds a new configuration option, add-message-id-if- missing (bool), through which you can control if a message id should be generated inside the message, or not. If you pick yes, Noffle works like it used to. If you choose no, it will not store a Message-ID: header in the text, but it will generate one to be able to store it in the outgoing queue. I've tested it locally, works like a charm ehre. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2006-06-27 16:05:45
|
Feature Requests item #1513395, was opened at 2006-06-27 15:48 Message generated for change (Settings changed) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: Jan De Luyck (devilkin) >Assigned to: Jim Hague (bears) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2006-06-27 15:27:37
|
Feature Requests item #1513426, was opened at 2006-06-27 17:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513426&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: Jan De Luyck (devilkin) Assigned to: Nobody/Anonymous (nobody) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513426&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2006-06-27 14:48:53
|
Feature Requests item #1513395, was opened at 2006-06-27 16:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Submitted By: Jan De Luyck (devilkin) Assigned to: Nobody/Anonymous (nobody) Summary: Disable message-id generation Initial Comment: Hello, I've got an account at astraweb, and unfortunately their servers are quite picky on how the message-id must be constructed. I've had trouble in the past with leafnode, and now with noffle, that the server will _not_ accept the msg- id generated by noffle. What I'd like to request is a way to tell noffle to not create a messageid, and just send the message as- is to the upstream server, so that the upstream server will generate a msgid for the message. Ofcourse, this would have to be used together with the post-locally entry, so that they can't be stored in the local spool. Thanks! Jan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=351044&aid=1513395&group_id=1044 |
|
From: Jim H. <jim...@ac...> - 2004-10-13 23:40:28
|
I've just checked in a couple of new items into CVS. Noffle will now log filter matches (though see below), and there's a new command line parameter, -U/--uninteresting that undoes the effect of reading an article; the article won't be downloaded unless read again. The logging could be nicer; in particular, regular expression matches merely report the match, and don't give the regular expression that they're matching. This is simply because at the moment Noffle doesn't carry the regular expression source around; rather, the RE is compiled at startup and the compiled version retained. I shall be tempted to make this 1.1.6. Though I might finally extract the digit far enough to add 'Xref' to the xover info first.... -- Jim Hague - jim...@ac... Never trust a computer you can't lift. |
|
From: SourceForge.net <no...@so...> - 2004-09-07 19:35:23
|
Bugs item #624357, was opened at 2002-10-17 00:14 Message generated for change (Settings changed) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=624357&group_id=1044 Category: None Group: None >Status: Closed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jim Hague (bears) Summary: SEGV during concurrent access. Initial Comment: My noffle 1.1.2 crashed during fetch. This happened while the connection had already been stuck (at step [17/19]) for some time, because I had some download taking up all bandwidth. I decided to read some news in the meantime but when I opened the newsgroup saar.markt.wohnung in the newsreader, noffle instantly crashed. I could not find any core dump lying around. This is not the only problem I had with concurrent access. I am using an automated script to archive news.answers using NNTP STAT followed by a NEXT loop until it gets a 223. Several times I read news while the script was running and it bailed out because it noticed the article ID had been reset to the first article in the group instead of being increased by NEXT to the next available article. Output of noffle: Fetch from 'news.cis.dfn.de' Connected to 130.133.1.4:119 Updating groupinfo Registering new group 'alt.pl.regionalne.plock.ogloszenia' Registering new group 'alt.pl.regionalne.poznan.politechnika' Registering new group 'alt.pl.regionalne.trojmiasto.ogloszenia' Registering new group 'alt.pl.regionalne.wroclaw.politechnika' Registering new group 'alt.pl.rock-elektroniczny' Registering new group 'alt.pl.sapkowski' Registering new group 'alt.pl.tsa' Registering new group 'alt.sports.college.ohio-state' Registering new group 'alt.sports.college.sec.tennessee' Registering new group 'alt.sports.college.utexas' Registering new group 'alt.tv.all-my-children' Registering new group 'alt.tv.dark_shadows' Getting remote overviews 5691-5693 for group alt.sys.pdp10 Added alt.sys.pdp10 3630-3632 3 articles marked for download in alt.sys.pdp10 Getting remote overviews 101021-101027 for group de.admin.net-abuse.mail Added de.admin.net-abuse.mail 87956-87962 7 articles marked for download in de.admin.net-abuse.mail Getting remote overviews 35102-35102 for group de.comm.internet.routing Added de.comm.internet.routing 28826-28826 1 articles marked for download in de.comm.internet.routing No new articles in de.comm.uucp No articles in maus.computer.sprache.gfabasic Getting remote overviews 240998-241005 for group news.answers Added news.answers 233839-233846 8 articles marked for download in news.answers Getting remote overviews 258-258 for group saar.markt.wohnung No new articles in saar.org.handshake.aktuell No new articles in saar.uni.rz.stud 19 TOTAL messages to download Retrieving article list [1/19] Retrieving <3kl...@ei...> [2/19] Retrieving <aokn1f$1ar6$1...@ci...> [3/19] Retrieving <5lo...@4a...> [4/19] Retrieving <aokici$20f$04$1...@ne...> [5/19] Retrieving <vni...@4a...> [6/19] Retrieving <8Yz...@zo...> [7/19] Retrieving <8YzDQ$Jt...@zo...> [8/19] Retrieving <aoklvd$8jk$03$1...@ne...> [9/19] Retrieving <gao...@4a...> [10/19] Retrieving <d8o...@4a...> [11/19] Retrieving <709...@us...> [12/19] Retrieving <de-admin-infos/dana-manual/200...@kr...> Message '<de-admin-infos/dana-manual/200...@kr...>' cancelled. [13/19] Retrieving <de-newusers-infos/einleitung/200...@kr...> Message '<de-newusers-infos/einleitung/200...@kr...>' cancelled. [14/19] Retrieving <usenet/inf...@rt...> Cancel: '<usenet/inf...@rt...>' not in database. [15/19] Retrieving <books/cat...@rt...> Cancel: '<books/cat...@rt...>' not in database. [16/19] Retrieving <sports/table-soccer/UST...@rt...> Cancel: '<sports/table-soccer/UST...@rt...>' not in database. [17/19] Retrieving <cdrom/cd-recordable/par...@rt...> Error opening /var/spool/noffle/data/articles.gdbm for r/w (Resource temporarily unavailable) Could not open database Retrieving of <cdrom/cd-recordable/par...@rt...> failed: Can't open message base Error opening /var/spool/noffle/data/articles.gdbm for r/w (Resource temporarily unavailable) Could not open database Error opening /var/spool/noffle/data/articles.gdbm for r/w (Resource temporarily unavailable) Could not open database Received SIGSEGV. Please submit a bug report Segmentation fault ---------------------------------------------------------------------- Comment By: Peter Backes (rtc1) Date: 2004-09-04 08:52 Message: Logged In: YES user_id=845643 Didn't happen anymore in the past two years, please close. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-10-26 08:49 Message: Logged In: NO Definitively no core, I ran find / -name core immediately after the crash (and by the way, it didn't say 'Segementation fault (core dumped)'). It's not a remote filesystem, it's the same filesystem as in '[ 532545 ] Strange behaviour adding large newsgroup'. ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2002-10-25 12:12 Message: Logged In: YES user_id=184 The second problem, losing the article pointer while reading a group, is now fixed in CVS. The SIGSEGV I can't do more than guess at without a backtrace. The core file should be at /var/spool/noffle/core. From the log, I am wondering about the 'Resource temporarily unavailable' message. /var/spool/noffle isn't a remote filesystem (e.g. NFS mounted) is it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=624357&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2004-09-07 19:34:48
|
Bugs item #532545, was opened at 2002-03-20 16:22 Message generated for change (Settings changed) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=532545&group_id=1044 Category: None Group: None >Status: Closed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jim Hague (bears) Summary: Strange behaviour adding large newsgroup Initial Comment: I'm using noffle-1.0.1 on Linux. Adding a newsgroup with a large number of articles and then fetching mails leads to strange behaviour which smells like a buffer overflow: root# noffle -S news.admin.net-abuse.email Adding news.admin.net-abuse.email to fetch list in full mode. root# noffle -f Fetch from 'news.cis.dfn.de' Connected to 130.133.1.4:119 Updating groupinfo No new articles in alt.sys.pdp10 No new articles in de.comm.uucp Missing articles (news.admin.net-abuse.email first=1460366 next=1443472) Cutting number of overviews to 32767 Getting remote overviews 1587578-1620344 for group news.admin.net-abuse.email Could not save group No such file or directory: ÔV Could not save group No such file or directory: ÕV Could not save group No such file or directory: ÖV Could not save group No such file or directory: ×V Could not save group No such file or directory: ØV Could not save group No such file or directory: ÙV Could not save group No such file or directory: ÚV Could not save group No such file or directory: ÛV Could not save group No such file or directory: ÜV Could not save group No such file or directory: ÝV Could not save group No such file or directory: ÞV Could not save group No such file or directory: ßV Could not save group No such file or directory: àV Could not save group No such file or directory: áV Could not save group No such file or directory: âV Could not save group No such file or directory: ãV Could not save group No such file or directory: äV Could not save group No such file or directory: åV Could not save group No such file or directory: æV Could not save group No such file or directory: çV Could not save group No such file or directory: èV Could not save group No such file or directory: éV Could not save group No such file or directory: êV Could not save group No such file or directory: ëV Could not save group No such file or directory: ìV Could not save group No such file or directory: íV Could not save group No such file or directory: îV Could not save group No such file or directory: ïV Could not save group No such file or directory: ðV Could not save group No such file or directory: ñV Could not save group No such file or directory: òV Could not save group No such file or directory: óV Could not save group No such file or directory: ôV Could not save group No such file or directory: õV Could not save group No such file or directory: öV Could not save group No such file or directory: ÷V Could not save group No such file or directory: øV Could not save group No such file or directory: ùV Could not save group No such file or directory: úV Could not save group No such file or directory: ûV Could not save group No such file or directory: üV Could not save group No such file or directory: ýV Could not save group No such file or directory: þV Could not save group No such file or directory: ÿV Could not save group No such file or directory: Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory:W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Would not save group No such file or directory: Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: !W Could not save group No such file or directory: "W Could not save group No such file or directory: #W Could not save group No such file or directory: $W Could not save group No such file or directory: %W Could not save group No such file or directory: &W Could not save group No such file or directory: 'W Could not save group No such file or directory: (W Could not save group No such file or directory: )W Could not save group No such file or directory: *W Could not save group No such file or directory: +W Could not save group No such file or directory: ,W Could not save group No such file or directory: -W Could not save group No such file or directory: .W Could not save group No such file or directory: /W Could not save group No such file or directory: 0W Could not save group No such file or directory: 1W Could not save group No such file or directory: 2W Could not save group No such file or directory: 3W Could not save group No such file or directory: 4W Could not save group No such file or directory: 5W Could not save group No such file or directory: 6W Could not save group No such file or directory: 7W Could not save group No such file or directory: 8W Could not save group No such file or directory: 9W Could not save group No such file or directory: :W Could not save group No such file or directory: ;W Could not save group No such file or directory: <W Could not save group No such file or directory: =W Could not save group No such file or directory: >W Could not save group No such file or directory: ?W Could not save group No such file or directory: @W Could not save group No such file or directory: AW Could not save group No such file or directory: BW Could not save group No such file or directory: CW Could not save group No such file or directory: DW Could not save group No such file or directory: EW Could not save group No such file or directory: FW Could not save group No such file or directory: GW Could not save group No such file or directory: HW Could not save group No such file or directory: IW Could not save group No such file or directory: JW Could not save group No such file or directory: KW Could not save group No such file or directory: LW Could not save group No such file or directory: MW Could not save group No such file or directory: NW Could not save group No such file or directory: OW Could not save group No such file or directory: PW Could not save group No such file or directory: QW Could not save group No such file or directory: RW Could not save group No such file or directory: SW Could not save group No such file or directory: TW Could not save group No such file or directory: UW Could not save group No such file or directory: VW Could not save group No such file or directory: WW Could not save group No such file or directory: XW Could not save group No such file or directory: YW Could not save group No such file or directory: ZW Could not save group No such file or directory: [W Could not save group No such file or directory: \W Could not save group No such file or directory: ]W Could not save group No such file or directory: ^W Could not save group No such file or directory: _W Could not save group No such file or directory: `W Could not save group No such file or directory: aW Could not save group No such file or directory: bW Could not save group No such file or directory: cW Could not save group No such file or directory: dW Could not save group No such file or directory: eW Could not save group No such file or directory: fW Could not save group No such file or directory: gW Could not save group No such file or directory: hW Could not save group No such file or directory: iW Could not save group No such file or directory: jW Could not save group No such file or directory: kW Could not save group No such file or directory: lW Could not save group No such file or directory: mW Could not save group No such file or directory: nW Could not save group No such file or directory: oW Could not save group No such file or directory: pW Could not save group No such file or directory: qW Could not save group No such file or directory: rW Could not save group No such file or directory: sW Could not save group No such file or directory: tW Could not save group No such file or directory: uW Could not save group No such file or directory: vW Could not save group No such file or directory: wW Could not save group No such file or directory: xW Could not save group No such file or directory: yW Could not save group No such file or directory: zW Could not save group No such file or directory: {W Could not save group No such file or directory: |W Could not save group No such file or directory: }W Could not save group No such file or directory: ~W Could not save group No such file or directory: W Could not save group No such file or directory: ?W Could not save group No such file or directory: ?W Could not save group No such file or directory: 'W Could not save group No such file or directory: W Could not save group No such file or directory: "W Could not save group No such file or directory: .W Could not save group No such file or directory: +W Could not save group No such file or directory: +W Could not save group No such file or directory: ^W Could not save group No such file or directory: %W Could not save group No such file or directory: SW Could not save group No such file or directory: <W Could not save group No such file or directory: OW Could not save group No such file or directory: ?W Could not save group No such file or directory: ZW Could not save group No such file or directory: ?W Could not save group No such file or directory: ?W Could not save group No such file or directory: 'W Could not save group No such file or directory: 'W Could not save group No such file or directory: "W Could not save group No such file or directory: "W Could not save group No such file or directory: W Could not save group No such file or directory: -W Could not save group No such file or directory: -W Could not save group No such file or directory: ~W Could not save group No such file or directory: TW Could not save group No such file or directory: sW Could not save group No such file or directory: >W Could not save group No such file or directory: oW Could not save group No such file or directory: ?W Could not save group No such file or directory: zW Could not save group No such file or directory: YW Could not save group No such file or directory: W Could not save group No such file or directory: ¡W Could not save group No such file or directory: ¢W Could not save group No such file or directory: £W Could not save group No such file or directory: ¤W Could not save group No such file or directory: ¥W Could not save group No such file or directory: ¦W Could not save group No such file or directory: §W Could not save group No such file or directory: ¨W Could not save group No such file or directory: ©W Could not save group No such file or directory: ªW Could not save group No such file or directory: «W Could not save group No such file or directory: ¬W Could not save group No such file or directory: W Could not save group No such file or directory: ®W Could not save group No such file or directory: ¯W Could not save group No such file or directory: °W Could not save group No such file or directory: ±W Could not save group No such file or directory: ²W Could not save group No such file or directory: ³W Could not save group No such file or directory: ´W Could not save group No such file or directory: µW Could not save group No such file or directory: ¶W Could not save group No such file or directory: ·W Could not save group No such file or directory: ¸W Could not save group No such file or directory: ¹W Could not save group No such file or directory: ºW Could not save group No such file or directory: »W Could not save group No such file or directory: ¼W Could not save group No such file or directory: ½W Could not save group No such file or directory: ¾W Could not save group No such file or directory: ¿W Could not save group No such file or directory: ÀW Could not save group No such file or directory: ÁW Could not save group No such file or directory: ÂW Could not save group No such file or directory: ÃW Could not save group No such file or directory: ÄW Could not save group No such file or directory: ÅW Could not save group No such file or directory: ÆW Could not save group No such file or directory: ÇW Could not save group No such file or directory: ÈW Could not save group No such file or directory: ÉW Could not save group No such file or directory: ÊW Could not save group No such file or directory: ËW Could not save group No such file or directory: ÌW Could not save group No such file or directory: ÍW Could not save group No such file or directory: ÎW Could not save group No such file or directory: ÏW Could not save group No such file or directory: ÐW Could not save group No such file or directory: ÑW Could not save group No such file or directory: ÒW Could not save group No such file or directory: ÓW Could not save group No such file or directory: ÔW Could not save group No such file or directory: ÕW Could not save group No such file or directory: ÖW Could not save group No such file or directory: ×W Could not save group No such file or directory: ØW Could not save group No such file or directory: ÙW Could not save group No such file or directory: ÚW Could not save group No such file or directory: ÛW Could not save group No such file or directory: ÜW Could not save group No such file or directory: ÝW Could not save group No such file or directory: ÞW Could not save group No such file or directory: ßW Could not save group No such file or directory: àW Could not save group No such file or directory: áW Could not save group No such file or directory: âW Could not save group No such file or directory: ãW Could not save group No such file or directory: äW Could not save group No such file or directory: åW Could not save group No such file or directory: æW Could not save group No such file or directory: çW Could not save group No such file or directory: èW Could not save group No such file or directory: éW Could not save group No such file or directory: êW Could not save group No such file or directory: ëW Could not save group No such file or directory: ìW Could not save group No such file or directory: íW Could not save group No such file or directory: îW Could not save group No such file or directory: ïW Could not save group No such file or directory: ðW Could not save group No such file or directory: ñW Could not save group No such file or directory: òW Could not save group No such file or directory: óW Could not save group No such file or directory: ôW Could not save group No such file or directory: õW Could not save group No such file or directory: öW Could not save group No such file or directory: ÷W Could not save group No such file or directory: øW Could not save group No such file or directory: ùW Could not save group No such file or directory: úW Could not save group No such file or directory: ûW Could not save group No such file or directory: üW Could not save group No such file or directory: ýW Could not save group No such file or directory: þW Could not save group No such file or directory: ÿW Could not save group No such file or directory: Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory:X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Xould not save group No such file or directory: Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: !X Could not save group No such file or directory: "X Could not save group No such file or directory: #X Could not save group No such file or directory: $X Could not save group No such file or directory: %X Could not save group No such file or directory: &X Could not save group No such file or directory: 'X Could not save group No such file or directory: (X Could not save group No such file or directory: )X Could not save group No such file or directory: *X Could not save group No such file or directory: +X Could not save group No such file or directory: ,X Could not save group No such file or directory: -X Could not save group No such file or directory: .X Could not save group No such file or directory: /X Could not save group No such file or directory: 0X Could not save group No such file or directory: 1X Could not save group No such file or directory: 2X Could not save group No such file or directory: 3X Could not save group No such file or directory: 4X Could not save group No such file or directory: 5X Could not save group No such file or directory: 6X Could not save group No such file or directory: 7X Could not save group No such file or directory: 8X Could not save group No such file or directory: 9X Could not save group No such file or directory: :X Could not save group No such file or directory: ;X Could not save group No such file or directory: <X Could not save group No such file or directory: =X Could not save group No such file or directory: >X Could not save group No such file or directory: ?X Could not save group No such file or directory: @X Could not save group No such file or directory: AX Could not save group No such file or directory: BX Could not save group No such file or directory: CX Could not save group No such file or directory: DX Could not save group No such file or directory: EX Could not save group No such file or directory: FX Could not save group No such file or directory: GX Could not save group No such file or directory: HX Could not save group No such file or directory: IX Could not save group No such file or directory: JX Could not save group No such file or directory: KX Could not save group No such file or directory: LX Could not save group No such file or directory: MX Could not save group No such file or directory: NX Could not save group No such file or directory: OX Could not save group No such file or directory: PX Could not save group No such file or directory: QX Could not save group No such file or directory: RX Could not save group No such file or directory: SX Could not save group No such file or directory: TX Received signal 2 (SIGINT). Aborting. (I hit ^C here.) ---------------------------------------------------------------------- Comment By: Peter Backes (rtc1) Date: 2004-09-04 08:51 Message: Logged In: YES user_id=845643 You can close this, it didn't occur anymore. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-23 01:19 Message: Logged In: NO I added both patches and recompiled with debug mode. I tried hard, but I'm unable to reproduce the behaviour again, obviously because the situation on the server side has changed. The first time I tried to reproduce it, I used the old database, which however already had the article counter for the group increased by the erroneous fetch, thus it didn't reduce the article count to 32767 and worked fine. I then erased any file in /var/spool/noffle and the contents of any of it's subdirectories to start with an untouched installation, loaded a new group list from the server, subscribed to the large group and finally fetched news. But it didn't provoke the misbehavior and again worked fine. Here's the output: [debug lines removed] Fetch from 'news.cis.dfn.de' Connected to 130.133.1.4:119 Updating groupinfo Cutting number of overviews to 32767 Getting remote overviews 1589305-1622071 for group news.admin.net-abuse.email Added news.admin.net-abuse.email 1460781-1486928 26148 articles marked for download in news.admin.net-abuse.email Retrieving article list Retrieving <9fn...@4a...> Retrieving <3C5...@ne....loopback> Retrieving <3C5...@cl...> Retrieving <1IR78.38440$Ni2.218793@news-ser [...] As you can see it still differs by missing one significant line from the erroneous fetch run: Missing articles (news.admin.net-abuse.email first=1460366 next=1443472) So I guess the error had something to do with this, maybe in conjunction with the download reduction to 32767 articles. Sorry if I wasn't of great help here. ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2002-03-21 09:27 Message: Logged In: YES user_id=184 OK. Looks like you should be OK. I'm not convinced we're seeing the right error message here. Would it be possible for you to try this and re-run? diff -c -r1.3.2.1 group.c *** group.c 17 Jul 2000 13:40:10 -0000 1.3.2.1 --- group.c 21 Mar 2002 09:08:23 -0000 *************** *** 57,64 **** static const char * errMsg( void ) { - if ( errno != 0 ) - return strerror( errno ); return gdbm_strerror( gdbm_errno ); } Also if you could re-run configure with --enable-debug=yes. After both those, re-run the fetch (kill it after the first Could not save group error) and upload the output. I'm wondering if the problem is some feature of a particular article. I'll try the same here against my upstream news server. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-20 18:21 Message: Logged In: NO Thanks for the patch. > However, there does seem to be something going wrong. > Do you have plenty of free disc space? I think I have enough. There's enough on /, which is relevant for the /tmp directory, /var for the noffle spool and /usr for the installed binaries. But judge yourself: root# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda5 132185 36354 89005 29% / /dev/hda6 513147 443600 43042 92% /usr /dev/hda7 513147 35489 451153 8% /var /dev/hda8 513147 217757 268885 45% /home/daemons /dev/hda9 2035606 1840165 90217 96% /home/localhost /dev/hda12 4036617 3687372 140402 97% /mnt/data /dev/hdb1 241763 227703 1575 100% /mnt/backup root# rpm -qvl noffle -rw------- news news 1776 Sep 16 2001 /etc/noffle.conf -rwsr-xr-x news news 141676 Sep 16 2001 /usr/bin/noffle drwxr-xr-x root wheel 1024 Sep 16 2001 /usr/doc/noffle-1.0.1 -rw-r--r-- root root 17989 May 5 2000 /usr/doc/noffle-1.0.1/COPYING -rw-r--r-- root root 26586 Jun 15 2001 /usr/doc/noffle-1.0.1/ChangeLog -rw-r--r-- root root 1546 May 5 2000 /usr/doc/noffle-1.0.1/FAQ -rw-r--r-- root root 11609 Feb 28 2001 /usr/doc/noffle-1.0.1/INSTALL -rw-r--r-- root root 5758 May 19 2000 /usr/doc/noffle-1.0.1/INTERNALS -rw-r--r-- root root 7127 Sep 10 2000 /usr/doc/noffle-1.0.1/NOTES -rw-r--r-- root root 2992 Feb 28 2001 /usr/doc/noffle-1.0.1/README -rw-r--r-- root root 1776 May 5 2000 /usr/doc/noffle-1.0.1/noffle.conf.example -rw-r--r-- root root 677 May 5 2000 /usr/doc/noffle-1.0.1/noffle.lsm -rw-r--r-- root wheel 2846 Sep 16 2001 /usr/man/man1/noffle.1.gz -rw-r--r-- root wheel 2479 Sep 16 2001 /usr/man/man5/noffle.conf.5.gz drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/data drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/lock drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/outgoing drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/overview drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/requested ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2002-03-20 17:29 Message: Logged In: YES user_id=184 Thanks for the report. The garbage characters at the end of each error message aren't the sign of a buffer overflow, but a coding error when printing the error message. If you're building from source, this patch should show the intended message: diff -c -r1.3.2.1 group.c *** group.c 17 Jul 2000 13:40:10 -0000 1.3.2.1 --- group.c 20 Mar 2002 17:28:48 -0000 *************** *** 146,152 **** val.dptr = buf; val.dsize = bufLen; if ( gdbm_store( grp.dbf, key, val, GDBM_REPLACE ) != 0 ) ! Log_err( "Could not save group %s: %s", errMsg() ); free( buf ); } --- 146,152 ---- val.dptr = buf; val.dsize = bufLen; if ( gdbm_store( grp.dbf, key, val, GDBM_REPLACE ) != 0 ) ! Log_err( "Could not save group %s: %s", grp.name, errMsg() ); free( buf ); } However, there does seem to be something going wrong. Do you have plenty of free disc space? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=532545&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2004-09-04 07:52:17
|
Bugs item #624357, was opened at 2002-10-17 01:14 Message generated for change (Comment added) made by rtc1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=624357&group_id=1044 Category: None Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jim Hague (bears) Summary: SEGV during concurrent access. Initial Comment: My noffle 1.1.2 crashed during fetch. This happened while the connection had already been stuck (at step [17/19]) for some time, because I had some download taking up all bandwidth. I decided to read some news in the meantime but when I opened the newsgroup saar.markt.wohnung in the newsreader, noffle instantly crashed. I could not find any core dump lying around. This is not the only problem I had with concurrent access. I am using an automated script to archive news.answers using NNTP STAT followed by a NEXT loop until it gets a 223. Several times I read news while the script was running and it bailed out because it noticed the article ID had been reset to the first article in the group instead of being increased by NEXT to the next available article. Output of noffle: Fetch from 'news.cis.dfn.de' Connected to 130.133.1.4:119 Updating groupinfo Registering new group 'alt.pl.regionalne.plock.ogloszenia' Registering new group 'alt.pl.regionalne.poznan.politechnika' Registering new group 'alt.pl.regionalne.trojmiasto.ogloszenia' Registering new group 'alt.pl.regionalne.wroclaw.politechnika' Registering new group 'alt.pl.rock-elektroniczny' Registering new group 'alt.pl.sapkowski' Registering new group 'alt.pl.tsa' Registering new group 'alt.sports.college.ohio-state' Registering new group 'alt.sports.college.sec.tennessee' Registering new group 'alt.sports.college.utexas' Registering new group 'alt.tv.all-my-children' Registering new group 'alt.tv.dark_shadows' Getting remote overviews 5691-5693 for group alt.sys.pdp10 Added alt.sys.pdp10 3630-3632 3 articles marked for download in alt.sys.pdp10 Getting remote overviews 101021-101027 for group de.admin.net-abuse.mail Added de.admin.net-abuse.mail 87956-87962 7 articles marked for download in de.admin.net-abuse.mail Getting remote overviews 35102-35102 for group de.comm.internet.routing Added de.comm.internet.routing 28826-28826 1 articles marked for download in de.comm.internet.routing No new articles in de.comm.uucp No articles in maus.computer.sprache.gfabasic Getting remote overviews 240998-241005 for group news.answers Added news.answers 233839-233846 8 articles marked for download in news.answers Getting remote overviews 258-258 for group saar.markt.wohnung No new articles in saar.org.handshake.aktuell No new articles in saar.uni.rz.stud 19 TOTAL messages to download Retrieving article list [1/19] Retrieving <3kl...@ei...> [2/19] Retrieving <aokn1f$1ar6$1...@ci...> [3/19] Retrieving <5lo...@4a...> [4/19] Retrieving <aokici$20f$04$1...@ne...> [5/19] Retrieving <vni...@4a...> [6/19] Retrieving <8Yz...@zo...> [7/19] Retrieving <8YzDQ$Jt...@zo...> [8/19] Retrieving <aoklvd$8jk$03$1...@ne...> [9/19] Retrieving <gao...@4a...> [10/19] Retrieving <d8o...@4a...> [11/19] Retrieving <709...@us...> [12/19] Retrieving <de-admin-infos/dana-manual/200...@kr...> Message '<de-admin-infos/dana-manual/200...@kr...>' cancelled. [13/19] Retrieving <de-newusers-infos/einleitung/200...@kr...> Message '<de-newusers-infos/einleitung/200...@kr...>' cancelled. [14/19] Retrieving <usenet/inf...@rt...> Cancel: '<usenet/inf...@rt...>' not in database. [15/19] Retrieving <books/cat...@rt...> Cancel: '<books/cat...@rt...>' not in database. [16/19] Retrieving <sports/table-soccer/UST...@rt...> Cancel: '<sports/table-soccer/UST...@rt...>' not in database. [17/19] Retrieving <cdrom/cd-recordable/par...@rt...> Error opening /var/spool/noffle/data/articles.gdbm for r/w (Resource temporarily unavailable) Could not open database Retrieving of <cdrom/cd-recordable/par...@rt...> failed: Can't open message base Error opening /var/spool/noffle/data/articles.gdbm for r/w (Resource temporarily unavailable) Could not open database Error opening /var/spool/noffle/data/articles.gdbm for r/w (Resource temporarily unavailable) Could not open database Received SIGSEGV. Please submit a bug report Segmentation fault ---------------------------------------------------------------------- Comment By: Peter Backes (rtc1) Date: 2004-09-04 09:52 Message: Logged In: YES user_id=845643 Didn't happen anymore in the past two years, please close. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-10-26 09:49 Message: Logged In: NO Definitively no core, I ran find / -name core immediately after the crash (and by the way, it didn't say 'Segementation fault (core dumped)'). It's not a remote filesystem, it's the same filesystem as in '[ 532545 ] Strange behaviour adding large newsgroup'. ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2002-10-25 13:12 Message: Logged In: YES user_id=184 The second problem, losing the article pointer while reading a group, is now fixed in CVS. The SIGSEGV I can't do more than guess at without a backtrace. The core file should be at /var/spool/noffle/core. From the log, I am wondering about the 'Resource temporarily unavailable' message. /var/spool/noffle isn't a remote filesystem (e.g. NFS mounted) is it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=624357&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2004-09-04 07:51:03
|
Bugs item #532545, was opened at 2002-03-20 17:22 Message generated for change (Comment added) made by rtc1 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=532545&group_id=1044 Category: None Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jim Hague (bears) Summary: Strange behaviour adding large newsgroup Initial Comment: I'm using noffle-1.0.1 on Linux. Adding a newsgroup with a large number of articles and then fetching mails leads to strange behaviour which smells like a buffer overflow: root# noffle -S news.admin.net-abuse.email Adding news.admin.net-abuse.email to fetch list in full mode. root# noffle -f Fetch from 'news.cis.dfn.de' Connected to 130.133.1.4:119 Updating groupinfo No new articles in alt.sys.pdp10 No new articles in de.comm.uucp Missing articles (news.admin.net-abuse.email first=1460366 next=1443472) Cutting number of overviews to 32767 Getting remote overviews 1587578-1620344 for group news.admin.net-abuse.email Could not save group No such file or directory: ÔV Could not save group No such file or directory: ÕV Could not save group No such file or directory: ÖV Could not save group No such file or directory: ×V Could not save group No such file or directory: ØV Could not save group No such file or directory: ÙV Could not save group No such file or directory: ÚV Could not save group No such file or directory: ÛV Could not save group No such file or directory: ÜV Could not save group No such file or directory: ÝV Could not save group No such file or directory: ÞV Could not save group No such file or directory: ßV Could not save group No such file or directory: àV Could not save group No such file or directory: áV Could not save group No such file or directory: âV Could not save group No such file or directory: ãV Could not save group No such file or directory: äV Could not save group No such file or directory: åV Could not save group No such file or directory: æV Could not save group No such file or directory: çV Could not save group No such file or directory: èV Could not save group No such file or directory: éV Could not save group No such file or directory: êV Could not save group No such file or directory: ëV Could not save group No such file or directory: ìV Could not save group No such file or directory: íV Could not save group No such file or directory: îV Could not save group No such file or directory: ïV Could not save group No such file or directory: ðV Could not save group No such file or directory: ñV Could not save group No such file or directory: òV Could not save group No such file or directory: óV Could not save group No such file or directory: ôV Could not save group No such file or directory: õV Could not save group No such file or directory: öV Could not save group No such file or directory: ÷V Could not save group No such file or directory: øV Could not save group No such file or directory: ùV Could not save group No such file or directory: úV Could not save group No such file or directory: ûV Could not save group No such file or directory: üV Could not save group No such file or directory: ýV Could not save group No such file or directory: þV Could not save group No such file or directory: ÿV Could not save group No such file or directory: Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory:W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Would not save group No such file or directory: Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: W Could not save group No such file or directory: !W Could not save group No such file or directory: "W Could not save group No such file or directory: #W Could not save group No such file or directory: $W Could not save group No such file or directory: %W Could not save group No such file or directory: &W Could not save group No such file or directory: 'W Could not save group No such file or directory: (W Could not save group No such file or directory: )W Could not save group No such file or directory: *W Could not save group No such file or directory: +W Could not save group No such file or directory: ,W Could not save group No such file or directory: -W Could not save group No such file or directory: .W Could not save group No such file or directory: /W Could not save group No such file or directory: 0W Could not save group No such file or directory: 1W Could not save group No such file or directory: 2W Could not save group No such file or directory: 3W Could not save group No such file or directory: 4W Could not save group No such file or directory: 5W Could not save group No such file or directory: 6W Could not save group No such file or directory: 7W Could not save group No such file or directory: 8W Could not save group No such file or directory: 9W Could not save group No such file or directory: :W Could not save group No such file or directory: ;W Could not save group No such file or directory: <W Could not save group No such file or directory: =W Could not save group No such file or directory: >W Could not save group No such file or directory: ?W Could not save group No such file or directory: @W Could not save group No such file or directory: AW Could not save group No such file or directory: BW Could not save group No such file or directory: CW Could not save group No such file or directory: DW Could not save group No such file or directory: EW Could not save group No such file or directory: FW Could not save group No such file or directory: GW Could not save group No such file or directory: HW Could not save group No such file or directory: IW Could not save group No such file or directory: JW Could not save group No such file or directory: KW Could not save group No such file or directory: LW Could not save group No such file or directory: MW Could not save group No such file or directory: NW Could not save group No such file or directory: OW Could not save group No such file or directory: PW Could not save group No such file or directory: QW Could not save group No such file or directory: RW Could not save group No such file or directory: SW Could not save group No such file or directory: TW Could not save group No such file or directory: UW Could not save group No such file or directory: VW Could not save group No such file or directory: WW Could not save group No such file or directory: XW Could not save group No such file or directory: YW Could not save group No such file or directory: ZW Could not save group No such file or directory: [W Could not save group No such file or directory: \W Could not save group No such file or directory: ]W Could not save group No such file or directory: ^W Could not save group No such file or directory: _W Could not save group No such file or directory: `W Could not save group No such file or directory: aW Could not save group No such file or directory: bW Could not save group No such file or directory: cW Could not save group No such file or directory: dW Could not save group No such file or directory: eW Could not save group No such file or directory: fW Could not save group No such file or directory: gW Could not save group No such file or directory: hW Could not save group No such file or directory: iW Could not save group No such file or directory: jW Could not save group No such file or directory: kW Could not save group No such file or directory: lW Could not save group No such file or directory: mW Could not save group No such file or directory: nW Could not save group No such file or directory: oW Could not save group No such file or directory: pW Could not save group No such file or directory: qW Could not save group No such file or directory: rW Could not save group No such file or directory: sW Could not save group No such file or directory: tW Could not save group No such file or directory: uW Could not save group No such file or directory: vW Could not save group No such file or directory: wW Could not save group No such file or directory: xW Could not save group No such file or directory: yW Could not save group No such file or directory: zW Could not save group No such file or directory: {W Could not save group No such file or directory: |W Could not save group No such file or directory: }W Could not save group No such file or directory: ~W Could not save group No such file or directory: W Could not save group No such file or directory: ?W Could not save group No such file or directory: ?W Could not save group No such file or directory: 'W Could not save group No such file or directory: W Could not save group No such file or directory: "W Could not save group No such file or directory: .W Could not save group No such file or directory: +W Could not save group No such file or directory: +W Could not save group No such file or directory: ^W Could not save group No such file or directory: %W Could not save group No such file or directory: SW Could not save group No such file or directory: <W Could not save group No such file or directory: OW Could not save group No such file or directory: ?W Could not save group No such file or directory: ZW Could not save group No such file or directory: ?W Could not save group No such file or directory: ?W Could not save group No such file or directory: 'W Could not save group No such file or directory: 'W Could not save group No such file or directory: "W Could not save group No such file or directory: "W Could not save group No such file or directory: W Could not save group No such file or directory: -W Could not save group No such file or directory: -W Could not save group No such file or directory: ~W Could not save group No such file or directory: TW Could not save group No such file or directory: sW Could not save group No such file or directory: >W Could not save group No such file or directory: oW Could not save group No such file or directory: ?W Could not save group No such file or directory: zW Could not save group No such file or directory: YW Could not save group No such file or directory: W Could not save group No such file or directory: ¡W Could not save group No such file or directory: ¢W Could not save group No such file or directory: £W Could not save group No such file or directory: ¤W Could not save group No such file or directory: ¥W Could not save group No such file or directory: ¦W Could not save group No such file or directory: §W Could not save group No such file or directory: ¨W Could not save group No such file or directory: ©W Could not save group No such file or directory: ªW Could not save group No such file or directory: «W Could not save group No such file or directory: ¬W Could not save group No such file or directory: W Could not save group No such file or directory: ®W Could not save group No such file or directory: ¯W Could not save group No such file or directory: °W Could not save group No such file or directory: ±W Could not save group No such file or directory: ²W Could not save group No such file or directory: ³W Could not save group No such file or directory: ´W Could not save group No such file or directory: µW Could not save group No such file or directory: ¶W Could not save group No such file or directory: ·W Could not save group No such file or directory: ¸W Could not save group No such file or directory: ¹W Could not save group No such file or directory: ºW Could not save group No such file or directory: »W Could not save group No such file or directory: ¼W Could not save group No such file or directory: ½W Could not save group No such file or directory: ¾W Could not save group No such file or directory: ¿W Could not save group No such file or directory: ÀW Could not save group No such file or directory: ÁW Could not save group No such file or directory: ÂW Could not save group No such file or directory: ÃW Could not save group No such file or directory: ÄW Could not save group No such file or directory: ÅW Could not save group No such file or directory: ÆW Could not save group No such file or directory: ÇW Could not save group No such file or directory: ÈW Could not save group No such file or directory: ÉW Could not save group No such file or directory: ÊW Could not save group No such file or directory: ËW Could not save group No such file or directory: ÌW Could not save group No such file or directory: ÍW Could not save group No such file or directory: ÎW Could not save group No such file or directory: ÏW Could not save group No such file or directory: ÐW Could not save group No such file or directory: ÑW Could not save group No such file or directory: ÒW Could not save group No such file or directory: ÓW Could not save group No such file or directory: ÔW Could not save group No such file or directory: ÕW Could not save group No such file or directory: ÖW Could not save group No such file or directory: ×W Could not save group No such file or directory: ØW Could not save group No such file or directory: ÙW Could not save group No such file or directory: ÚW Could not save group No such file or directory: ÛW Could not save group No such file or directory: ÜW Could not save group No such file or directory: ÝW Could not save group No such file or directory: ÞW Could not save group No such file or directory: ßW Could not save group No such file or directory: àW Could not save group No such file or directory: áW Could not save group No such file or directory: âW Could not save group No such file or directory: ãW Could not save group No such file or directory: äW Could not save group No such file or directory: åW Could not save group No such file or directory: æW Could not save group No such file or directory: çW Could not save group No such file or directory: èW Could not save group No such file or directory: éW Could not save group No such file or directory: êW Could not save group No such file or directory: ëW Could not save group No such file or directory: ìW Could not save group No such file or directory: íW Could not save group No such file or directory: îW Could not save group No such file or directory: ïW Could not save group No such file or directory: ðW Could not save group No such file or directory: ñW Could not save group No such file or directory: òW Could not save group No such file or directory: óW Could not save group No such file or directory: ôW Could not save group No such file or directory: õW Could not save group No such file or directory: öW Could not save group No such file or directory: ÷W Could not save group No such file or directory: øW Could not save group No such file or directory: ùW Could not save group No such file or directory: úW Could not save group No such file or directory: ûW Could not save group No such file or directory: üW Could not save group No such file or directory: ýW Could not save group No such file or directory: þW Could not save group No such file or directory: ÿW Could not save group No such file or directory: Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory:X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Xould not save group No such file or directory: Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: X Could not save group No such file or directory: !X Could not save group No such file or directory: "X Could not save group No such file or directory: #X Could not save group No such file or directory: $X Could not save group No such file or directory: %X Could not save group No such file or directory: &X Could not save group No such file or directory: 'X Could not save group No such file or directory: (X Could not save group No such file or directory: )X Could not save group No such file or directory: *X Could not save group No such file or directory: +X Could not save group No such file or directory: ,X Could not save group No such file or directory: -X Could not save group No such file or directory: .X Could not save group No such file or directory: /X Could not save group No such file or directory: 0X Could not save group No such file or directory: 1X Could not save group No such file or directory: 2X Could not save group No such file or directory: 3X Could not save group No such file or directory: 4X Could not save group No such file or directory: 5X Could not save group No such file or directory: 6X Could not save group No such file or directory: 7X Could not save group No such file or directory: 8X Could not save group No such file or directory: 9X Could not save group No such file or directory: :X Could not save group No such file or directory: ;X Could not save group No such file or directory: <X Could not save group No such file or directory: =X Could not save group No such file or directory: >X Could not save group No such file or directory: ?X Could not save group No such file or directory: @X Could not save group No such file or directory: AX Could not save group No such file or directory: BX Could not save group No such file or directory: CX Could not save group No such file or directory: DX Could not save group No such file or directory: EX Could not save group No such file or directory: FX Could not save group No such file or directory: GX Could not save group No such file or directory: HX Could not save group No such file or directory: IX Could not save group No such file or directory: JX Could not save group No such file or directory: KX Could not save group No such file or directory: LX Could not save group No such file or directory: MX Could not save group No such file or directory: NX Could not save group No such file or directory: OX Could not save group No such file or directory: PX Could not save group No such file or directory: QX Could not save group No such file or directory: RX Could not save group No such file or directory: SX Could not save group No such file or directory: TX Received signal 2 (SIGINT). Aborting. (I hit ^C here.) ---------------------------------------------------------------------- Comment By: Peter Backes (rtc1) Date: 2004-09-04 09:51 Message: Logged In: YES user_id=845643 You can close this, it didn't occur anymore. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-23 02:19 Message: Logged In: NO I added both patches and recompiled with debug mode. I tried hard, but I'm unable to reproduce the behaviour again, obviously because the situation on the server side has changed. The first time I tried to reproduce it, I used the old database, which however already had the article counter for the group increased by the erroneous fetch, thus it didn't reduce the article count to 32767 and worked fine. I then erased any file in /var/spool/noffle and the contents of any of it's subdirectories to start with an untouched installation, loaded a new group list from the server, subscribed to the large group and finally fetched news. But it didn't provoke the misbehavior and again worked fine. Here's the output: [debug lines removed] Fetch from 'news.cis.dfn.de' Connected to 130.133.1.4:119 Updating groupinfo Cutting number of overviews to 32767 Getting remote overviews 1589305-1622071 for group news.admin.net-abuse.email Added news.admin.net-abuse.email 1460781-1486928 26148 articles marked for download in news.admin.net-abuse.email Retrieving article list Retrieving <9fn...@4a...> Retrieving <3C5...@ne....loopback> Retrieving <3C5...@cl...> Retrieving <1IR78.38440$Ni2.218793@news-ser [...] As you can see it still differs by missing one significant line from the erroneous fetch run: Missing articles (news.admin.net-abuse.email first=1460366 next=1443472) So I guess the error had something to do with this, maybe in conjunction with the download reduction to 32767 articles. Sorry if I wasn't of great help here. ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2002-03-21 10:27 Message: Logged In: YES user_id=184 OK. Looks like you should be OK. I'm not convinced we're seeing the right error message here. Would it be possible for you to try this and re-run? diff -c -r1.3.2.1 group.c *** group.c 17 Jul 2000 13:40:10 -0000 1.3.2.1 --- group.c 21 Mar 2002 09:08:23 -0000 *************** *** 57,64 **** static const char * errMsg( void ) { - if ( errno != 0 ) - return strerror( errno ); return gdbm_strerror( gdbm_errno ); } Also if you could re-run configure with --enable-debug=yes. After both those, re-run the fetch (kill it after the first Could not save group error) and upload the output. I'm wondering if the problem is some feature of a particular article. I'll try the same here against my upstream news server. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-20 19:21 Message: Logged In: NO Thanks for the patch. > However, there does seem to be something going wrong. > Do you have plenty of free disc space? I think I have enough. There's enough on /, which is relevant for the /tmp directory, /var for the noffle spool and /usr for the installed binaries. But judge yourself: root# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda5 132185 36354 89005 29% / /dev/hda6 513147 443600 43042 92% /usr /dev/hda7 513147 35489 451153 8% /var /dev/hda8 513147 217757 268885 45% /home/daemons /dev/hda9 2035606 1840165 90217 96% /home/localhost /dev/hda12 4036617 3687372 140402 97% /mnt/data /dev/hdb1 241763 227703 1575 100% /mnt/backup root# rpm -qvl noffle -rw------- news news 1776 Sep 16 2001 /etc/noffle.conf -rwsr-xr-x news news 141676 Sep 16 2001 /usr/bin/noffle drwxr-xr-x root wheel 1024 Sep 16 2001 /usr/doc/noffle-1.0.1 -rw-r--r-- root root 17989 May 5 2000 /usr/doc/noffle-1.0.1/COPYING -rw-r--r-- root root 26586 Jun 15 2001 /usr/doc/noffle-1.0.1/ChangeLog -rw-r--r-- root root 1546 May 5 2000 /usr/doc/noffle-1.0.1/FAQ -rw-r--r-- root root 11609 Feb 28 2001 /usr/doc/noffle-1.0.1/INSTALL -rw-r--r-- root root 5758 May 19 2000 /usr/doc/noffle-1.0.1/INTERNALS -rw-r--r-- root root 7127 Sep 10 2000 /usr/doc/noffle-1.0.1/NOTES -rw-r--r-- root root 2992 Feb 28 2001 /usr/doc/noffle-1.0.1/README -rw-r--r-- root root 1776 May 5 2000 /usr/doc/noffle-1.0.1/noffle.conf.example -rw-r--r-- root root 677 May 5 2000 /usr/doc/noffle-1.0.1/noffle.lsm -rw-r--r-- root wheel 2846 Sep 16 2001 /usr/man/man1/noffle.1.gz -rw-r--r-- root wheel 2479 Sep 16 2001 /usr/man/man5/noffle.conf.5.gz drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/data drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/lock drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/outgoing drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/overview drwxr-sr-x news news 1024 Sep 16 2001 /var/spool/noffle/requested ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2002-03-20 18:29 Message: Logged In: YES user_id=184 Thanks for the report. The garbage characters at the end of each error message aren't the sign of a buffer overflow, but a coding error when printing the error message. If you're building from source, this patch should show the intended message: diff -c -r1.3.2.1 group.c *** group.c 17 Jul 2000 13:40:10 -0000 1.3.2.1 --- group.c 20 Mar 2002 17:28:48 -0000 *************** *** 146,152 **** val.dptr = buf; val.dsize = bufLen; if ( gdbm_store( grp.dbf, key, val, GDBM_REPLACE ) != 0 ) ! Log_err( "Could not save group %s: %s", errMsg() ); free( buf ); } --- 146,152 ---- val.dptr = buf; val.dsize = bufLen; if ( gdbm_store( grp.dbf, key, val, GDBM_REPLACE ) != 0 ) ! Log_err( "Could not save group %s: %s", grp.name, errMsg() ); free( buf ); } However, there does seem to be something going wrong. Do you have plenty of free disc space? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=532545&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2003-11-29 23:29:04
|
Bugs item #851342, was opened at 2003-11-29 23:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=851342&group_id=1044 Category: None Group: None Status: Open Priority: 5 Submitted By: Jim Hague (bears) Assigned to: Jim Hague (bears) Summary: Can't specify default user/group at configure time Initial Comment: You can't specify the default user/group at configure time. This means that if your system doesn't have user news group news (e.g. it's CygWin) then make install fails. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=851342&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2003-07-18 23:54:25
|
Bugs item #756585, was opened at 2003-06-18 06:24 Message generated for change (Settings changed) made by greydmiyu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 Category: None Group: None >Status: Closed Priority: 5 Submitted By: Steve Lamb (greydmiyu) Assigned to: Jim Hague (bears) Summary: Noffle cannot handle @ in the username Initial Comment: My ISP outsources news to Supernews. My login through that route is use...@is... and not just username. Noffle cannot handle that in the configuration file. root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Fetch from 'news.foobar.com' finished If I place quotes around the username the quotes are sent to the remote side. root@teleute:/etc/news# vim noffle.conf root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Password rejected. Server status: 502 no permission (no match for 'ex...@fo...') Connection to remote server lost (article numbers could be inconsistent) Fetch from 'news.foobar.com' finished ---------------------------------------------------------------------- Comment By: Jim Hague (bears) Date: 2003-06-18 08:20 Message: Logged In: YES user_id=184 Thanks for the bug report. I don't see the problem here. Or not the problem you're describing, at any rate. Noffle can't cope if the username contains a space or tab, and if that becomes a problem I'll need to update the config file parser to cope with quoted strings. But in this case your login seems to be working pefectly. The 'Unknown argument -q news.foobar.com' message is because you have the command wrong. It should be either 'noffle -q groups news.foobar.com' or 'noffle -q desc news.foobar.com'. There *is* a bug in the code here; if neither is given Noffle should just stop. But I stuffed up, so in fact it continues after issuing the error and connects to the server, logging in successfully in the first instance, and then disconnects without actually fetching anything. I'll fix this soon. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2003-06-18 15:20:18
|
Bugs item #756585, was opened at 2003-06-18 14:24 Message generated for change (Comment added) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 Category: None Group: None Status: Open Priority: 5 Submitted By: Steve Lamb (greydmiyu) Assigned to: Jim Hague (bears) Summary: Noffle cannot handle @ in the username Initial Comment: My ISP outsources news to Supernews. My login through that route is use...@is... and not just username. Noffle cannot handle that in the configuration file. root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Fetch from 'news.foobar.com' finished If I place quotes around the username the quotes are sent to the remote side. root@teleute:/etc/news# vim noffle.conf root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Password rejected. Server status: 502 no permission (no match for 'ex...@fo...') Connection to remote server lost (article numbers could be inconsistent) Fetch from 'news.foobar.com' finished ---------------------------------------------------------------------- >Comment By: Jim Hague (bears) Date: 2003-06-18 16:20 Message: Logged In: YES user_id=184 Thanks for the bug report. I don't see the problem here. Or not the problem you're describing, at any rate. Noffle can't cope if the username contains a space or tab, and if that becomes a problem I'll need to update the config file parser to cope with quoted strings. But in this case your login seems to be working pefectly. The 'Unknown argument -q news.foobar.com' message is because you have the command wrong. It should be either 'noffle -q groups news.foobar.com' or 'noffle -q desc news.foobar.com'. There *is* a bug in the code here; if neither is given Noffle should just stop. But I stuffed up, so in fact it continues after issuing the error and connects to the server, logging in successfully in the first instance, and then disconnects without actually fetching anything. I'll fix this soon. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2003-06-18 15:04:26
|
Bugs item #756585, was opened at 2003-06-18 14:24 Message generated for change (Settings changed) made by bears You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 Category: None Group: None Status: Open Priority: 5 Submitted By: Steve Lamb (greydmiyu) >Assigned to: Jim Hague (bears) Summary: Noffle cannot handle @ in the username Initial Comment: My ISP outsources news to Supernews. My login through that route is use...@is... and not just username. Noffle cannot handle that in the configuration file. root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Fetch from 'news.foobar.com' finished If I place quotes around the username the quotes are sent to the remote side. root@teleute:/etc/news# vim noffle.conf root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Password rejected. Server status: 502 no permission (no match for 'ex...@fo...') Connection to remote server lost (article numbers could be inconsistent) Fetch from 'news.foobar.com' finished ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 |
|
From: SourceForge.net <no...@so...> - 2003-06-18 13:24:14
|
Bugs item #756585, was opened at 2003-06-18 06:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 Category: None Group: None Status: Open Priority: 5 Submitted By: Steve Lamb (greydmiyu) Assigned to: Nobody/Anonymous (nobody) Summary: Noffle cannot handle @ in the username Initial Comment: My ISP outsources news to Supernews. My login through that route is use...@is... and not just username. Noffle cannot handle that in the configuration file. root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Fetch from 'news.foobar.com' finished If I place quotes around the username the quotes are sent to the remote side. root@teleute:/etc/news# vim noffle.conf root@teleute:/etc/news# noffle -q news.foobar.com Unknown argument -q news.foobar.com Fetch from 'news.foobar.com' Connected to 216.168.3.50:119 Password rejected. Server status: 502 no permission (no match for 'ex...@fo...') Connection to remote server lost (article numbers could be inconsistent) Fetch from 'news.foobar.com' finished ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101044&aid=756585&group_id=1044 |
|
From: Jim H. <jim...@ac...> - 2003-03-25 14:53:33
|
On 25-Mar-2003 joh...@gm... wrote: > But than we have to ensure that the user has a directory in /etc/, not > just a file. We would have to change CONFIGFILE to CONFIGDIR and of > course make some minor corrections now and then. True. But Debian have already moved that way, and there's no reason we can't look for noffle.conf in /etc/noffle and then /etc to keep backwards compatability. -- Jim Hague - jim...@in... (Work), ji...@be... (Play) Never trust a computer you can't lift. |
|
From: <joh...@gm...> - 2003-03-25 14:22:44
|
On Mon, Mar 24, 2003 at 11:53:26PM -0000, Jim Hague wrote:
> On 24-Mar-2003 joh...@gm... wrote:
> > I think I could assist in internationalization of the
> > noffle-pseude-articles (those messages getting return in pseudo.c).
> > With this patch it would be possible to have a french, german and
> > english version of e.g. the "article marked for download".
> >
> > There are some decisions I would like to get examined before I start to code.
> >
> > +I would suggest to have a file in /etc/noffle/noffle.articles.{ccTLD},
> > {ccTLD} being the country-Top-Level-Domain for the country generally
> > associated with that language, e.g. de for german, fr for france ...
> >
> I think it would be easier to have one file per message, perhaps filed under a
> language-specific directory, e.g. /etc/noffle/templates.en_GB/general_info.
> Specify the language in the config file, or pick it up from the environment
> (LANG) if it is not specified in the config. Then see if a file exists in
> this order (for LANG=en_GB): templates.en_GB/filename, templates.en/filename,
> templates/filename. Keep the current hard-coded defaults in case none are
> found.
But than we have to ensure that the user has a directory in /etc/, not
just a file. We would have to change CONFIGFILE to CONFIGDIR and of
course make some minor corrections now and then.
So long...
Johannes Madel
|
|
From: <joh...@gm...> - 2003-03-25 09:18:07
|
Hi Folks I forgot, that the templates should be editable by the user, so forget about that "lets-put-it-in-an-mo-file"...:-) So long... Johannes Madel |
|
From: <joh...@gm...> - 2003-03-25 09:15:45
|
Hi Folks
another question: Why dont we just put a file into
/usr/share/locale/{language}/ (under debian), next to all those other
*.mo files ?
So long...
Johannes Madel
|
|
From: Jim H. <jim...@ac...> - 2003-03-24 23:53:31
|
On 24-Mar-2003 joh...@gm... wrote:
> I think I could assist in internationalization of the
> noffle-pseude-articles (those messages getting return in pseudo.c).
> With this patch it would be possible to have a french, german and
> english version of e.g. the "article marked for download".
>
> There are some decisions I would like to get examined before I start to code.
>
> +I would suggest to have a file in /etc/noffle/noffle.articles.{ccTLD},
> {ccTLD} being the country-Top-Level-Domain for the country generally
> associated with that language, e.g. de for german, fr for france ...
>
I think it would be easier to have one file per message, perhaps filed under a
language-specific directory, e.g. /etc/noffle/templates.en_GB/general_info.
Specify the language in the config file, or pick it up from the environment
(LANG) if it is not specified in the config. Then see if a file exists in
this order (for LANG=en_GB): templates.en_GB/filename, templates.en/filename,
templates/filename. Keep the current hard-coded defaults in case none are
found.
Describe the template format in a new man page noffle.template.
> Problem: The are maybe some languages which are not specific to a
> country (what was the Top-Level-Domain for Esperanto again ;-) ) and
> maybe in some country more than language is officially used.
> Question: How shall we determine which user gets his message in which
> language. Should there be a global "noffle-now-be-german"-switch in the
> config-file ? Should we default german pseudo messages for e.g.
> de.*-newsgroups ?
I don't think we can do anything about trying to decide on a per-user basis.
NNTP tells us nothing about the user. Environments that need to support
multiple languages amongst their users will simply have to have multi-lingual
messages.
> This noffle.articles.{ccTLD} file would have the folloing format
> message_entry = ' < ' message-designator ' > ' \n message-text
> message-designator = 'text'
> message-text = 'text'
Having each message in its own file saves all sorts of syntax. We can just have
the message pretty much as it will appear (once a few extra headers are added).
Subject: [ NOFFLE: Article counter inconsistent ]
This group's article counter is not consistent.
Probably the remote news server ...
Don't forget that we need to be able to insert values into the messages, e.g.
the 'retrieve failed' message. I suggest this is done by some sort of variable
substitution, e.g. (for the inconsistent count message):
Group: $GROUP
Remote first article number: $REMOTE_FIRST
Remote last article number: $REMOTE_LAST
Remove next article number: $REMOTE_NEXT
Refetching from article: $REFETCH_FROM
--
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift or you don't control.
|
|
From: <joh...@gm...> - 2003-03-24 23:11:33
|
Hi Folks
I think I could assist in internationalization of the
noffle-pseude-articles (those messages getting return in pseudo.c).
With this patch it would be possible to have a french, german and
english version of e.g. the "article marked for download".
There are some decisions I would like to get examined before I start to code.
+I would suggest to have a file in /etc/noffle/noffle.articles.{ccTLD},
{ccTLD} being the country-Top-Level-Domain for the country generally
associated with that language, e.g. de for german, fr for france ...
Problem: The are maybe some languages which are not specific to a
country (what was the Top-Level-Domain for Esperanto again ;-) ) and
maybe in some country more than language is officially used.
I agree that the filename noffle.articles is quite long. But bear in
mind, that we also need a manpage for this file and it would be quite
... arrogant for noffle to demand such a general word for its manpage
Question: How shall we determine which user gets his message in which
language. Should there be a global "noffle-now-be-german"-switch in the
config-file ? Should we default german pseudo messages for e.g.
de.*-newsgroups ?
This noffle.articles.{ccTLD} file would have the folloing format
message_entry = ' < ' message-designator ' > ' \n message-text
message-designator = 'text'
message-text = 'text'
I decided against the standart varX = valueY syntax because I think a
big part in message-text will be newline caracters and the escaping
those would not really help to make the file more readable. I also
decided against the windows-init-file-syntax
[section1]
foo
bar
because I have seen in in the pseudo messages are also a lot of [s and
]s.
But actually I am not really happy with this syntax. I'll think over it
again. Maybe someone else has a good idea.
So long...
Johannes Madel
|
|
From: Jim H. <jim...@ac...> - 2003-03-21 11:32:05
|
On 20-Mar-2003 joh...@gm... wrote: > I would like to assist you developing noffle. Excellent! Thank you. > I know that working together in an open-source project involves a great deal > of self-responsibile working, but currently I feel that I need some help > nevertheless. If you haven't already, please join the noffle-devel mailing list. This is the list for Noffle developers. It's pretty quiet, so don't worry about being drowned in traffic. Oh, and asking before you launch into anything is always a good idea on any project. > I read the latest TODO list in the current cvs-repository but the two > "urgent" items on this list do not seem to be the "trivial job" for the > unskilled worker. I agree that * Deal properly with headers split over several lines where the overall content of the header exceeds MAXCHAR characters (i.e. length of Str). will be a non-trivial change and isn't a great place to start. But * Post: Only generate Reply-To: from From: if a configuration option set. should be pretty simple. Reply-To generation happens at line 323 in post.c. You'd need to add a new configuration access routine in configfile.h/configfile.c; see the existing Bool routines, e.g. Cfg_autoSubscribe(). The other thing on the list I would like to see done is some localisation work. In particular, the pseudo-messages Noffle generates - e.g. the 'I'm not fetching that group right now, but I will start' message - have their content and subject hard-coded in English in pseudo.c. I would like to see that text taken from files in /etc/noffle that the sysadmin can configure for local conditions. I would also like to have standard translations for other languages. Keep the hard-coded contents in case the message files don't exist. Also, possibly we should search for the message files by first appending the locale to the name, and picking up that file if it exists. The next stage would be internationalisation of the Noffle source, so that the usage message, error messages and even the log messages can have translations provided. This should be a straightforward use of the GNU gettext() mechanism. > By the way, is there a downloadable mbox archive file of the > mailinglist noffle-users ? Not that I know of. > P.s: I wrote this email in english, though I have noticed nearly all > team-members have their email-address in de domainspace. If the language > in which you use to conversate is german, please let me know There is a heavy German presence. Unfortunately, there's also one 'unwissendes Englander mit nur Schule Deutschem', sufficient to see if Babelfish looks sort-of plausible but nothing more. Me. So, (sorry) English please? And if you're not that confident in your English, don't worry - I'm just sorry I have such minimal German. -- Jim Hague - jim...@in... (Work), ji...@be... (Play) Never trust a computer you can't lift. |
|
From: Jim H. <jim...@ac...> - 2003-03-20 10:26:00
|
On 19-Mar-2003 Simon Bell wrote: > Ive been trying to set up noffle to use stunnel to accept connections on > port 563. > > Noffle works fine running without stunnel on port 119. I've got Noffle set up this way on one of my machines. I'm still using old inetd, so I can't help on xinetd configuration details. I'm using stunnel 3.22. Here's the relevant line in my inetd.conf: nntps stream tcp nowait root /usr/sbin/stunnel stunnel -r localhost:nntp That being said, I am little puzzled by your configuration: > service nntp Is that a typo? I assume it is, 'cos you say Noffle on 119 is working normally. I presume you mean nntps. I'm also a little puzzled by these: > server = /usr/sbin/stunnel > server_args = -d nntps -l /usr/local/bin/noffle -- noffle Your stunnel.conf would seem to imply that you're asking stunnel to connect incoming nntps connections to 119. In which case xinetd will start noffle as normal, because it will see an incoming connection on 119 (from stunnel). So I think your server_args need to be different; in fact, looking at the stunnel 4 man page (there is no stunnel.conf in stunnel 3), it looks like you don't need arguments at all. So try with 'server = /usr/sbin/stunnel' and no server_args line. What I suggest is you first make sure Noffle is working properly on 119. Can you read news via a normal NNTP connection? If you can, then try the nntps configuration. If it doesn't work, then asking on the stunnel lists for help is the thing to do; the problem will be one of stunnel config. -- Jim Hague - jim...@in... (Work), ji...@be... (Play) Never trust a computer you can't lift or you don't control. |
65 messages has been excluded from this view by a project administrator.
