[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #FNS-542635]: not started

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #FNS-542635]: not started
  • Date: Fri, 07 Aug 2015 10:35:25 -0600
Patrick,

Your top(1) looks Ok. What's the output of the command "top -b -n 1"?

> Patrick,
> 
> Sweet! I didn't know about the free(1) utility.
> 
> Unfortunately, that utility isn't available on all Unix systems (Solaris 
> doesn't have it, for example). The top(1) utility is more widespread -- so I 
> use it.
> ---
> That's got to be a serious pain for you dude :/    was going to recommend 
> uptime for the cpu portion instead of top, but what you just said above 
> obviously would apply :/
> ---
> 
> I'd like know why ldmadmin(1) isn't getting what it needs from your top(1). 
> Would you please send me the output of the following commands:
> 
> uname -a
> top -\?
> regutil | grep top
> 
> ---
> ldm@crad1:~$ uname -a
> Linux crad1 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 GNU/Linux
> ldm@crad1:~$ top -\?
> top: unknown option '?'
> usage:  top -hv | -bcHiSs -d delay -n limit -u|U user | -p pid[,pid] -w [cols]
> ldm@crad1:~$ regutil | grep top
> /metrics/top-command : /usr/bin/top -b -n 1
> ldm@crad1:~$
> ---
> 
> Cheers,
> 
> --patrick


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FNS-542635
Department: Support LDM
Priority: Normal
Status: Closed