[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Pan-users] Re: Error message
From: |
Beartooth |
Subject: |
[Pan-users] Re: Error message |
Date: |
Thu, 12 Jan 2006 13:02:12 -0500 |
User-agent: |
Pan/0.14.2.91 (As She Crawled Across the Table) |
On Tue, 10 Jan 2006 17:54:51 -0700, Duncan wrote:
> beartooth posted
> <address@hidden>,
> excerpted below, on Tue, 10 Jan 2006 16:51:28 -0500:
>
>
>>
>> I get this one very often, and have no idea what it means, nor what to
>> do about it :
>>
>> Mon, 09 Jan 2006 12:44:39 - (Null) - Parse error at '@adelphia.net':
>> expected ',' Mon, 09 Jan 2006 12:44:39 - (Null) - Parse error at
>> '@adelphia.net': expected ',' Mon, 09 Jan 2006 12:44:41 - (Null) - Parse
>> error at '@adelphia.net': expected ','
>
> Interesting. That's an error I don't think I've seen. Further, just from
> memory anyway, IDR any header that would use commas for separation that
> would also use email addresses, thus the @adelphia.net portion. The
> newsgroups header separates with commas, but wouldn't have the @ notation.
> The from and reply-to headers would have the @ notation but aren't likely
> to have multiple addresses or use commas. The references and path headers
> have multiple entries and references in particular might use @, but they
> aren't separated with commas...
>
> If you had the post in question it might be helpful, but it might be
> difficult to get it as PAN probably is skipping those posts due to the
> parse errors. Perhaps try with knode or the like, and compare what gets
> shown to figure out which messages knode shows that PAN doesn't?
>
> It's also possible you might be able to get more debugging info by running
> PAN from a terminal window (konsole, gterm, xterm, whatever), possibly
> with one or more debug parameters (try pan --help for the list).
OK, I looked that and then opened a terminal in which I commanded "pan
--debug" -- while leaving my regular Pan open. It poured messages
beginning with "TRACE" at me. When they stopped, I cut it off with Ctrl-^,
but left the terminal open. Is there something to look for in general, or
do I wait and do it again when I see one of the odd error messages in
regular Pan? Or just leave it running and watch for that one to show up?
Or ...? What I knokw of debugging would go in a gnat's eye ...
--
Beartooth Stickster, Neo-Redneck Linux Enthusiast
A wanderstaff like an Elvish rope should be long,
and strong, and light -- and very smooth.