Re: [OT] Exit status (was Re: getmail bug reported: failed to work with procmail or maildrop)

2002-01-19 Thread Charles Jie
Hi, Derek, Thank you very much for your example and patient explanation. That's pretty helpful. It's clear enough, while I also check wait(2) for complete document. (I have no that book. Maybe go buy it if it's pretty good.) I'm trying to find out what the exit code 0xB4 means. best, charlie

Re: getmail bug reported: failed to work with procmail or maildrop

2002-01-19 Thread Charles Cazabon
Charles Jie <[EMAIL PROTECTED]> wrote: > > Fix the bug by replacing the 'poll' with 'wait' in > /usr/lib/getmail/getmail.py. > > Now my getmail does a good job. Noted. Will include in next release. Why is procmail taking so long for you, though? > I've tried to use maildrop other than p

[OT] Exit status (was Re: getmail bug reported: failed to work with procmail or maildrop)

2002-01-18 Thread Derek D. Martin
At some point hitherto, Charles Jie hath spake thusly: > > > Aborting... (command "/usr/bin/maildrop ~/.maildroprc" returned 19200 (maildrop: >signal 0x06)) > > > > > > I can not explain the 'returned 19200'. For someone's exercise. ;-) > > > > It's the exit code and the signal, encoded in a

Re: getmail bug reported: failed to work with procmail or maildrop

2002-01-18 Thread Charles Jie
On Fri, Jan 18, 2002 at 04:05:51PM -0600, Charles Cazabon wrote: > Charles Jie <[EMAIL PROTECTED]> wrote: > > > > Fix the bug by replacing the 'poll' with 'wait' in > > /usr/lib/getmail/getmail.py. > > > > Now my getmail does a good job. > > Noted. Will include in next release. Why is procmail