> "KB" == Karl Berry writes:
KB> Not on this Debian, it appears.
KB> vcs(20)#$ top -w 128
KB> top: unknown argument 'w'
It must have been added in procps 3.3. Squeeze only has 3.2.
You are right about COLUMNS, though. It looks like the maximum width of
the command is 512. (Combined w
> If the width is an issue, use something like -w128 for 128 columns.
Not on this Debian, it appears.
vcs(20)#$ top -w 128
top: unknown argument 'w'
However, I think it looks for the COLUMNS envvar (undocumented; not sure).
Anyway, I've set that now, we'll see if it helps. Not that a
Argh. I wasn't fast enough to catch that before it got out.
> If the width is an issue, use something like -w128 for 128 columns.
That should be all you need to do.
Ignore the earlier content (or /non/-content, as it were :(.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
> "KB" == Karl Berry writes:
KB> Unfortunately top does not show the full command line (argh),
Try adding the -c flag. (Or removing it.)
Modern top will use the saved config for that user, with options like -c
toggling.
Older top may not do that, but -c still should either enable the full
Regarding sv load, as mentioned, /var/tmp/toplog on vcs has been
accumulating top snapshots every 20 minutes for a while now. (BTW,
there is also /var/log/atop.log*, set up by someone else long ago, but I
didn't research how to do anything with that.)
I just looked at it for the last week. The l
Bob Proulx wrote:
> Karl Berry wrote:
> > I know Bob et al. were gathering stats on frontend, but I didn't see
> > anything on vcs.
>
> The firewalls on the machines were blocking me from setting it up on
> vcs. I am going to open the firewalls to allow it. Originally I
> didn't understand how t
Karl Berry wrote:
> I know Bob et al. were gathering stats on frontend, but I didn't see
> anything on vcs.
The firewalls on the machines were blocking me from setting it up on
vcs. I am going to open the firewalls to allow it. Originally I
didn't understand how they were set up. But now I unde
~ Jan 2013 it experience long delays with a good consistency when
starting at 07:25 and 12:25 UTC (they are still there today).
That is good information. And the timing seems like it might relate.
Ward, I wonder about using --bwlimit as well as nice on the backup job.
That's the first gu
Hi Karl,
On Mon, Sep 02, 2013 at 04:09:09PM +, Karl Berry wrote:
> When I looked at vcs this morning, the load average was around 15. I
> just ran top, and it was because of this rsync job, which had already
> been running for over an hour (the start time is UTC today):
>
> USER PID P
