Knode double-posting (was Re: OT: Newbie question: Currentdirectory in path?)
in [Slackware]
|
Prev: Newbie question: Current directory in path?
Next: Knode double-posting (was Re: OT: Newbie question: Current directory in path?)
From: Sylvain Robitaille on 16 Jul 2010 01:00 Lew Pitcher wrote: > In this case, Knode hung while sending the message. I killed it, > restarted Knode, and resent the message properly. > > Apparently, Knode's first attempt was successful. It just didn't > return fast enough (10 seconds is enough wait time, don't you think?) > to tell me that it had sent the message. Ah, but perhaps you're pointing the finger at the wrong bit of software? Perhaps knode was still waiting for the news server to acknowledge having received the message? > And, of course, my 2nd attempt put a second message out there. Does Knode have any option that would have it generate its own message IDs for messages you post? If it does, and you enable that, that should help avoid the double postings. A news server (at least those I knew whan I was a news admin ... I actually miss that task) expects every post to have a unique message-id, so that duplicates are automatically avoided. > Sometimes I wonder about all this ;-) Which part? -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: Sylvain Robitaille on 16 Jul 2010 10:46 Lew Pitcher wrote: > ... I doubt that knode is the culprit here; I've often had problems > with my ISP's outsourced nntp provider, and it wouldn't surprise me > that this is another one of them. Try waiting longer than 10 seconds. It may simply be that the server is particularly busy at times, and if that coincides with when you post your message, depending on the system, I could see it take longer than that. > A "dumb user", however, would know little or nothing of NNTP server > issues, and would care even less. To /that user/, the face of NNTP is > Knode, and Knode didn't respond (to the user) fast enough. A minor > quibble, to be certain, and one that doesn't apply to me. You say it doesn't apply to you, yet it's clearly how you reacted (you killed Knode and started over because Knode didn't respond in 10 seconds or less). You may not be a "dumb user", yet that's more reason NOT to give "dumb user" explanations. This next part is still relevant: >> Does Knode have any option that would have it generate its own >> message IDs for messages you post? ... >>> Sometimes I wonder about all this ;-) >> >> Which part? > > Mostly, my ISP's outsourced NNTP service. NNTP/NNRP are generally I/O bound, so it's not surprising that the service might seem slow at times. Netnews has long ago been cast aside by ISPs, as an expense, rather than a revenue-generating service. It used to be they enticed customers with that service. Now they grudgingly offer an outsourced version instead. The outsourcers are most certainly not getting rich with this service. All this is to say that this isn't the service that tends to get the most powerful I/O subsystems. -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: Sylvain Robitaille on 17 Jul 2010 01:45
Grant wrote: > Was it Leafnode? Could have been, but it's your system. You tell us ... > Can you recommend an app that caches two outside servers to cover for > the non-responding one? I've never tried to use it with two outside servers, but you might want to have a look at slrnpull, which will be in the slrn package of your favourite Linux distribution. I used that when my ISP connection was via dialup (and I had it pull from the news server I was managing, so I wasn't particularly inclined to try other servers). Ever since broadband came along, that's simply become less useful to me. -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ---------------------------------------------------------------------- |