BB Unix Network Monitor - Message
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: {bb} bb-iostat + debian
- To: <bb@bb4.com>
- Subject: RE: {bb} bb-iostat + debian
- From: "Kimberly McKinnis" <kmckinnis@macrovision.com>
- Date: Sat, 24 Sep 2005 02:43:31 -0700
- Content-class: urn:content-classes:message
- Content-transfer-encoding: 8bit
- Content-type: text/plain; charset="us-ascii"
- Reply-to: bb@bb4.com
- Sender: owner-bb@bb4.com
- Thread-index: AcXAg6hTNZyqD/HTTt2bKAGraU1O9QACX4cw
- Thread-topic: {bb} bb-iostat + debian
Hahaha. I completely forgot about that. Because I was googling for
debian + iostat, it never came up. Everytime I install BB on a different
distro, I run into issues. Guess I can't blame Debian this time.
The corresponding web page was showing a lot of blank info. I will set
the debug flag and see what happens.
What would I do without you, Phil? Can I send you some cookies or
something? :)
-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Philip
Clark
Sent: Friday, September 23, 2005 1:25 PM
To: bb@bb4.com
Subject: Re: {bb} bb-iostat + debian
On Fri, 2005-09-23 at 01:58, Kimberly McKinnis wrote:
> Is anyone running bb-iostat with Debian? It's throwing errors into
BBOUT
> but I can't track them down.
>
>
>
> Thu Sep 22 17:13:32 2005 bb-iostat.sh
> /usr/local/bb/bbc1.9e-btf/ext/bb-iostat.sh: procs: command not found
>
> Thu Sep 22 17:13:32 2005 bb-iostat.sh
> /usr/local/bb/bbc1.9e-btf/ext/bb-iostat.sh: 0: command not found
>
> Thu Sep 22 17:13:40 2005 bb-iostat.sh
> /usr/local/bb/bbc1.9e-btf/ext/bb-iostat.sh: [: too many arguments
>
>
>
> Procs command? I can't find anything called procs in the script. And
the
> others are quite vague. I've double checked that all the paths are
> correct.
Deja vu :)
http://support.bb4.com/archive/200505/msg00107.html
>From some of the other messages in the archive, it looks like
problems with the output from the iostat part can cause a
errors in the vmstat part. The "procs" thing looks like it
comes from the header of the vmstat output, which is being
mis-interpreted.
What is the corresponding web page showing? If there's nothing
instructive reported there, the next step would probably be
to set the "WDebug" flag (and select an output in the DECHO
routine).
Cheers, Phil.
--
I went into a general store, and they wouldn't sell me anything
specific. (Steven Wright)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.
Home |
Main Index |
Thread Index