From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.162.5 with SMTP id xw5csp435600vdb; Fri, 2 Aug 2013 06:55:55 -0700 (PDT) X-Received: by 10.60.150.241 with SMTP id ul17mr5306702oeb.69.1375451755536; Fri, 02 Aug 2013 06:55:55 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id mu7si4370705obc.49.2013.08.02.06.55.55 for ; Fri, 02 Aug 2013 06:55:55 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (bad format) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id D55C74B184; Fri, 2 Aug 2013 13:47:15 +0000 (UTC) Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by rubyforge.org (Postfix) with ESMTP id B0C5C2E145 for ; Tue, 30 Jul 2013 13:26:15 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id i10so11031485oag.30 for ; Tue, 30 Jul 2013 06:26:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=asVXOtI0YykCZDdadNs8Tzkhto35okKmag8o1FEemcs=; b=wEz+ugq7ShvxDMGQSMaIRN9zOKS3VhT5XR+WQb9OwKZqi883GcACvHPoPzmRt41p9O 5kMiKr0sH/4xY77UQyUYTnshm2uFp7GGWHVadCJlf1FIp6RNiJGOadKdq18LGHpErmoX Kb4qNf38I+wNaZazGCxc40OBgLtl/etYwZIuTD+x/xUaJ1wFbHOn4uAUU0ev7fIeQbLb yMLRTNWlm4WFBHlTL65L2xd2jVhSPq3sMn2MsWsLslIpWQo6iGXME47PCzXOwDLVUCz3 bEZrUHC3g3v/ELZv72qT+pQeuQVE9IFABQU0JFnOR88iSMHZt4Qv6cUYhIdAo07Ye7Hq 4S8w== MIME-Version: 1.0 X-Received: by 10.182.220.199 with SMTP id py7mr57134693obc.92.1375190307408; Tue, 30 Jul 2013 06:18:27 -0700 (PDT) Received: by 10.182.199.69 with HTTP; Tue, 30 Jul 2013 06:18:27 -0700 (PDT) Date: Tue, 30 Jul 2013 22:18:27 +0900 Message-ID: From: Horacio Sanson To: Sup developer discussion Subject: [sup-devel] How do I force flush the log file in sup? X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0626662708833707135==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============0626662708833707135== Content-Type: multipart/alternative; boundary=001a11c334aac5932704e2ba7154 --001a11c334aac5932704e2ba7154 Content-Type: text/plain; charset=ISO-8859-1 Is there a way to force sup to flush the log file after each write? It is difficult to debug my gmail source as I cannot see real time what is going on. Maybe set sup to always flush when SUP_LOG_LEVEL is set to debug? regards, Horacio --001a11c334aac5932704e2ba7154 Content-Type: text/html; charset=ISO-8859-1
Is there a way to force sup to flush the log file after each write? It is difficult to debug my gmail source as I cannot see real time what is going on. Maybe set sup to always flush when SUP_LOG_LEVEL is set to debug?

regards,
Horacio
--001a11c334aac5932704e2ba7154-- --===============0626662708833707135== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel --===============0626662708833707135==--