Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 24 Mar 2005 05:21:51 -0800 From: George To: cygwin AT cygwin DOT com Subject: Re: fetchmail -v Not Verbose Enough Message-ID: <20050324132151.GA1412@home> Reply-To: George Mail-Followup-To: cygwin AT cygwin DOT com References: <20050322161221 DOT GA1112 AT home> <20050322165656 DOT GA3068 AT tishler DOT net> <20050322190606 DOT GB1112 AT home> <20050323010002 DOT GA3972 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050323010002.GA3972@tishler.net> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes 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/