Received: by oss.sgi.com id ; Wed, 22 Nov 2000 00:38:04 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:35701 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 22 Nov 2000 00:37:54 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id AAA02621 for ; Wed, 22 Nov 2000 00:29:56 -0800 (PST) mail_from (markgw@sgi.com) Received: from sandpit.melbourne.sgi.com (sandpit.melbourne.sgi.com [134.14.55.132]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA24655; Wed, 22 Nov 2000 19:35:13 +1100 Date: Wed, 22 Nov 2000 19:35:13 +1100 (EST) From: Mark Goodwin X-Sender: markgw@sandpit.melbourne.sgi.com To: Michal Kara cc: pcp@oss.sgi.com Subject: Re: PMLogger question/suggestion In-Reply-To: <20001122090114.B5811@arthur.plbohnice.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-pcp@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pcp-outgoing Content-Length: 2052 Lines: 49 On Wed, 22 Nov 2000, Michal Kara wrote: > > From what I can gather, you should use a Makefile to drive cpp in the > > /var/pcp/config/pmlogger directory. > > I have created such Makefile. It is universal - it takes all .src files and > preprocesses them and it also automagically handles dependencies. I can send it > to you, if you are interested. yes please. There would be no harm in including it in the pcp distro. As with your previous contributions, you need to give it to SGI before I can include it in the distribution. > > > I think all of this pmlogger management stuff you need is already > > available. Check out the man page for pmlogger_check(1). This is an > > extensible cron based pcp archive log management infrastructure driven > > by the control file in /var/pcp/config/pmlogger/control. Suitable/example > > cron entries are in /var/pcp/config/pmlogger/crontab. > > What I wanted to have is command "restart pmlogger for server > host1.domain.com". But it is not too complicated, I realized that the names of > the servers are in commandline of the process, so "ps x | grep pmlogger" and > then kill the process works. so this is a "kill and then restart" situation, right? pmlogger_check will only only start the pmloggers if they have died or not running ... > (I use pmlogger_check and pmlogger_daily and also > my own script to merge all logs for each of the monitored hosts (made when pcp > restarted or pmda went down...)) pmlogger_daily and/or pmlogger_merge should be enough to merge the daily logs .. but knowing you, your own script was necessary ;-) > > > That is far too much CPU time for such a low fetch rate. Can you send me your > > pmlogger configs and/or gprof /var/pcp/pmdas/linux/pmdalinux (this is the > > daemon form of the linux PMDA dso, so you can profile it. You'll need to > > edit /var/pcp/config/pmcd/pmcd.conf to change from DSO to daemon). > > Hmpf, it is much better today (???) Maybe some kind of error... If it appears > again, I will investigate it... > ok thanks -- Mark