| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | sosreport and pcp |
| From: | Michele Baldessari <michele@xxxxxxxxxx> |
| Date: | Tue, 29 Apr 2014 15:15:02 +0100 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/simple; d=acksyn.org; h= user-agent:content-disposition:content-type:content-type :mime-version:message-id:subject:subject:from:from:date:date :received:received; s=2010; t=1398780903; bh=dUi43A8GDasam7RJZhy RDya38pww07ZzswQWBbFgXdE=; b=FIoOi5v+p5o1I0/pd7IvvCoS0ZI7siPnXse PX9STJX55qa9eO4PdDpoEnEM47CRNGvZNxO+1VkR3J47WOVRMBIIRvTDyhDh32h3 EwfW+ANNSjCJCp+oBvEjdg1eHEyI/sMPpy/7jLFZ8+BFEK0+SWK76xORTzn5WvFp Fs3vbyLo= |
| User-agent: | Mutt/1.5.21 (2012-12-30) |
Hi all, I am in the process of adding support for PCP in sosreport[1]. Here is the list of files that, from a first glance, sosreport should collect in order to be able to troubleshoot PCP questions/issues: /var/log/pcp, /var/lib/pcp/config, /etc/pcp, /etc/pcp.conf, /etc/pcp.env, /etc/pcp.sh Are there any other files or directory or output of commands that you can think of that are needed when troubleshooting PCP? I'd imagine that extra carefulness needs to be taken for /var/log/pcp in order to avoid collecting stuff (logger data?) that is bigger than X unless explicitely asked for. I assume they can grow moderately big, although I don't have any real-world data on that. Thanks for any inputs and or feedback on this. Kind regards, Michele [1] https://github.com/sosreport/sos -- Michele Baldessari <michele@xxxxxxxxxx> C2A5 9DA3 9961 4FFB E01B D0BC DDD4 DCCB 7515 5C6D |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: docs, getopts, Nathan Scott |
|---|---|
| Next by Date: | Re: sosreport and pcp, Frank Ch. Eigler |
| Previous by Thread: | pcp updates: docs, getopts, Nathan Scott |
| Next by Thread: | Re: sosreport and pcp, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |