The man page for vmstat shows that the parameters are "delay" and "count". So, for:
vmstat 300 2
it should give the first line of info, pause five minutes, then give the second line, then exit. Try it in a terminal window and see... In other words, it goes away anyway of its own accord, 5 minutes after it started.
Ralph Mitchell
On 6/6/06, Charles Jones <jonescr at cisco.com> wrote:
when I do ./hobbit.sh stop, vmstat is not killed: $ ps xw |grep hobbit 26903 ? S 0:00 sh -c vmstat 300 2 1>/users/monitor/local/hobbit/client/tmp/hobbit_vmstat.my-host.26883 2>&1; mv /users/monitor/local/hobbit/client/tmp/hobbit_vmstat.my-host.26883 /users/monitor/local/hobbit/client/tmp/hobbit_vmstat.my-host
I noticed that if I do several "hobbit.sh restart", there will be extra vmstat processes running. For now I am manually killing them via "pkill vmstat" (on linux), after I stop or restart Hobbit.
-Charles
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk