05-29-2009
did you checked the file nfs_kdes.ext is linked to /usr/lib/drivers/nfs_kdes_null.ext???
nfs_kdes.ext -> /usr/lib/drivers/nfs_kdes_null.ext
10 More Discussions You Might Find Interesting
1. AIX
good morning
what is the better solution to examen a P570 ?
because i use topas and nmon, and the results are totally different !!!
with nmon, i have 80% free cpu, and with nmon, i have 90% of used cpu !!!!!!
i take a shot with an intervall of 10s during 10 mn.
thank you (0 Replies)
Discussion started by: pascalbout
0 Replies
2. AIX
Anyone ever experienced a core dump when running NMON. I am running AIX 5.3 on an 8 CPU LPAR (P570). This has only recently started to happen. (3 Replies)
Discussion started by: johnf
3 Replies
3. AIX
Can any one help where i can find articals about nomn
I need to know how to read this tools
┌─CPU-Utilisation-Small-View───────────────────────────────────────────────────┐
│ 0----------25-----------50----------75----------100│
│CPU User% Sys% Wait% Idle%| ... (3 Replies)
Discussion started by: habuzahra
3 Replies
4. AIX
HI Im new on this world.
Im working with nmon and I understand that this tool generates a files that later with excel I can see the graphcial of my server.
The problem is that this process is execute manualy and I need to meake automatic.
How can I do That.
Sorry for my english!! :o (3 Replies)
Discussion started by: jegtoro
3 Replies
5. AIX
Hi All,
I have a p550 server with 4 proc. But when i run nmon analyzer in cpu_sum it show 5 processors cpu0 cpu1 cpu2 cpu3 cpu4. Why it is showing 5 processors. (6 Replies)
Discussion started by: vjm
6 Replies
6. AIX
HI,
I have downloaded nmon 3.3c nmon analyzer, and run the command on aix ./nmon -f
After that I have terminated the process and found .nmon file.
when i have tried to open that file in nmon analyzer i.e in excel I am getting the error "no valid input data nmon run may have failed"
... (8 Replies)
Discussion started by: manoj.solaris
8 Replies
7. Red Hat
Hi guys,
as per subject i am setting up NMON for the above OS but it is 64-bit Linux.
I downloaded the 32-bit NMON for RHEL45 as it is the only one available for RHEL45.
However, I ran into problem with the binary file.
# ./nmon_x86_rhel45
./nmon_x86_rhel45: error while loading shared... (13 Replies)
Discussion started by: DrivesMeCrazy
13 Replies
8. AIX
Hi guys, I am an Oracle DBA and I have an account with some databases on an AIX 5.3 server. I am trying to figure out if I really need to add memory to this box or not, the account team keeps pushing me to make a decision and I don't want to waste their money if I don't need to right now, we could... (4 Replies)
Discussion started by: nibbsbitt
4 Replies
9. Shell Programming and Scripting
Hi, my name is Steve Ngai from Malaysia. This is my first post. Hope to learn more about Unix from this forum.
My first question is can nmon be customized? When I run nmon, I need to manually type c to see CPU usage, then m for memory usage. Can I pass it some nmon option to automatically see... (2 Replies)
Discussion started by: ngaisteve1
2 Replies
10. AIX
Hi all,
I am currently having trouble to get nmon to print me the actual CPU usage for an interval for a process.
According to the manual, something like
# time nmon -t -C cron -s 5 -c 2 -F outfile
real 0m0.98s
user 0m0.03s
sys 0m0.04s
should print out at least the process... (15 Replies)
Discussion started by: zaxxon
15 Replies
LEARN ABOUT DEBIAN
dh-exec
DH-EXEC(1) dh-exec DH-EXEC(1)
NAME
dh-exec - Debhelper executable file helpers
SYNOPSIS
#! /usr/bin/dh-exec
src/libfoo-*.so.* debian/foo-plugins/usr/lib/foo/${DEB_HOST_MULTIARCH}/
etc/example.conf => debian/foo/etc/foo/foo.conf
DESCRIPTION
dh-exec is a simple program, meant to be used as the interpreter for executable debhelper config files.
It is a wrapper around the various other sub-commands (see below), and will pipe the input file through all of them in turn, using an
ordering that makes most sense in the vast majority of cases.
The order as of now is dh-exec-subst gets run first, followed by dh-exec-install, so that variable expansion happens before files need to
be copied.
ARCHITECTURE
dh-exec is built up from three layers: there is the dh-exec utility, its single entry point, the only thing one will need to call.
Below that, there are the various sub-commands, such as dh-exec-subst, dh-exec-installs and dh-exec-illiterate, which are thin wrappers
around the various dh-exec scripts, that make sure they only run those that need to be run.
And the lowest layer are the various scripts that do the actual work.
One can control which sub-commands to run, or if even more granularity is desired, one can limit which scripts shall be run, too. See below
for the options!
OPTIONS
--with=command[,command ...]
Replace the list of sub-commands to run the input through with a custom list (where entries are separated by whitespace or commas).
This option will always replace the existing list with whatever is specified.
This can be used to explicitly set which sub-commands to use.
The list must not include the dh-exec- prefix.
Defaults to subst,install.
--without=command[,command ...]
Inversely to the option above, this lists all the sub-commands which should not be used.
The list must not include the dh-exec- prefix.
--with-scripts=script[,script ...]
Replace the list of scripts to run the input through with a custom list (where entries are separated by whitespace or commas). This
option will always replace the existing list with whatever is specified.
This can be used to explicitly specify which scripts to use, limiting even beyond what the --with option is capable of.
The list must not include the dh-exec- prefix.
By default it is empty, meaning there is no filtering done, and whatever scripts the sub-commands find, will be run.
--no-act
Do not really do anything, but print the pipeline that would have been run instead.
--list
List the available sub-commands and scripts, grouped by sub-command.
--help, --version
Display a short help or the package version, respectively.
SUB-COMMANDS
dh-exec-subst
Substitutes various variables (either from the environment, or from dpkg-architecture(1)).
dh-exec-install
An extension to dh_install(1), that supports renaming files during the copy process, using a special syntax.
ENVIRONMENT
DH_EXEC_LIBDIR
The directory in which the wrapped sub-commands reside. Defaults to /usr/lib/dh-exec/.
DH_EXEC_SCRIPTDIR
The directory in which the scripts that do the heavy work live. Defaults to /usr/share/dh-exec/.
FILES
$DH_EXEC_LIBDIR/dh-exec-*
The various sub-commands.
$DH_EXEC_SCRIPTDIR/dh-exec-*
The various scripts ran by the sub-commands.
SEE ALSO
debhelper(1), dh-exec-subst(1), dh-exec-install(1)
AUTHOR
dh-exec is copyright (C) 2011-2012 by Gergely Nagy <algernon@madhouse-project.org>.
2012-05-03 DH-EXEC(1)