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: Tue, 22 Mar 2005 20:00:03 -0500 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: fetchmail -v Not Verbose Enough Message-ID: <20050323010002.GA3972@tishler.net> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050322190606.GB1112@home> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes 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: > > > I've since decided I'm too creative with wasting time so I thought > > > I'd start using the daemon mode. That worked fine, too, but now > > > I've since discovered that if fetchmail is run manually, the > > > verbose option produces no output. > > > > Did you check your fetchmail log file? > > 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. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/