On Tue, Mar 22, 2005 at 08:00:03PM -0500, Jason Tishler wrote: > George, > > On Tue, Mar 22, 2005 at 11:06:06AM -0800, George wrote: > > On Tue, Mar 22, 2005 at 11:56:56AM -0500, Jason Tishler wrote: > > > On Tue, Mar 22, 2005 at 08:12:21AM -0800, George wrote: > > Thanks for the reply, Jason. Sure, everything's there. Procamail is > > working, too. What's throwing for a loop is this sudden disappearance > > of screen output when running fetchmail manually with the verbose > > option set. I can find a workaround if necessary and monitor the > > fetchmail log directly, but it would be nice to clearup this oddity. > > AFAICT, this is not a Cygwin fetchmail issue, so you may want to try the > fetchmail list to find a better workaround -- if one exists.
I should have had a closer look at (a euphemism for "actually read") the log file. The log file didn't exist prior to running fetchmail in daemon mode, as evidenced by the first line: fetchmail: starting fetchmail 6.2.5 daemon All subsequent invocations of fetchmail (fetchmail -v) generated log entries only. Manually removing the log file allows the -v option to function normally and generate screen output. Executing 'touch /var/log/fetchmail.log' recreates the no-screen-output behaviour and status messages are again redirected to the log file. I haven't looked closely enough (another euphemism, but this one for "I'm too lazy at the moment") at fetchmail's various logging options (I have none set in ~/.fetchmailrc), so I'll leave the issue as to whether this is a fetchmail problem to you. Cheers. -- George -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
