04-21-2009
is the server patched with latest patch cluster? which solaris release is installed?
10 More Discussions You Might Find Interesting
1. Solaris
Good morning,
I need some help figuring out what's eating up my cpu. My application can't get enough cpu to do its job. this is a sunfire V440 2CPU's at 1/593 GHZ with 8GB of memory. In the morning hours the box is at less than 3%. I can't figure out what else is using the CPU. We use foglight and... (2 Replies)
Discussion started by: bbouhaik
2 Replies
2. AIX
Hi am facing high cpu utilization on my sybase server.
I have P550
Number Of Processors: 4
Processor Clock Speed: 1656 MHz
CPU Type: 64-bit
Kernel Type: 32-bit
LPAR Info: 1 65-D837E
Memory Size: 7840 MB
in topas it shows
Name PID CPU% PgSp Owner
dataserv 565264 ... (1 Reply)
Discussion started by: vjm
1 Replies
3. Shell Programming and Scripting
Hi All,
i have a script that finds the file with .txt .zip .Z .gzip that are 3 days old in directory /abc/def and removes them
find /abc/def -name '0*.txt' -mtime +6 -exec rm {} \;
find /abc/def -name '0*.zip' -mtime +6 -exec rm {} \;
find /abc/def -name '0*.gzip' -mtime +6... (3 Replies)
Discussion started by: mad_man12
3 Replies
4. Shell Programming and Scripting
There is a script which processes the incoming files from a particular directory and sleeps if it doesnt find any. Currently, i have been told that eventhough there are no files to process, the CPU utilization is very high. An independent evaluation by advisory specialist has found this script does... (2 Replies)
Discussion started by: nandu
2 Replies
5. Solaris
Hi,
I am working on a solaris app processor and the vsh goes high from time to time. I have executed various ps commands and switches and have found that it looks like the rlogind daemon is terminating vsh and not cleaning up after itself. There are also something like 10 zombies hanging around... (2 Replies)
Discussion started by: troystevens
2 Replies
6. UNIX for Advanced & Expert Users
good morning.
just wanted to ask if there's a way to check what causes the high cpu utilization of a server for the past 2 months? My jffnms report resulted to high utilization for a specific server last month. is there a way to check via a command line?
thanks (9 Replies)
Discussion started by: lhareigh890
9 Replies
7. Infrastructure Monitoring
Dear Gentleman
in my environment I have Solaris10 OS Box in Global Zone with 136 GB and mount point from SAN Storage 500 GB (Orastorage)
Zone1 mounted on /Zones folder with 66 GB
when I run zpool list output
-bash-3.00$ zpool list
NAME SIZE ALLOC FREE CAP HEALTH... (0 Replies)
Discussion started by: Hosam
0 Replies
8. Shell Programming and Scripting
Hello all,
I am very new to unix and trying to solve this problem.
I have cluster of 3 nodes. when I run TOP command on each server, I see a two GZIP processess with very high CPU utilization even,if I don't go backups or unzipping.
Can somebody tell me what is the problem, I don't want... (1 Reply)
Discussion started by: nnani
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
i am observing few processes taking high CPU and when i got some more detials about them it looks like this
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9452 xmp 25 0 16736 1224 860 R 100.0 0.0 903:54.18 ffmpeg -i -
9777 xmp 25 0 16736 1224 ... (1 Reply)
Discussion started by: Siddheshk
1 Replies
10. Red Hat
Hi Experts,
I need to understand few basic things regarding top command result from one of the node i have collected:
Cpu0 : 4.6%us, 2.0%sy, 0.0%ni, 91.4%id, 1.3%wa, 0.3%hi, 0.3%si, 0.0%st
Cpu1 : 0.0%us, 0.3%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : ... (5 Replies)
Discussion started by: mackjack87
5 Replies
LEARN ABOUT DEBIAN
dpatch.make
DPATCH.MAKE(7) dpatch DPATCH.MAKE(7)
NAME
dpatch.make - simplistic wrapper around dpatch(1) for make(1).
SYNOPSIS
include /usr/share/dpatch/dpatch.make
DESCRIPTION
For backwards compatibility and ease of use, dpatch.make is provided along with dpatch(1). Its purpose is to implement generic patch and
unpatch rules that can be reused in debian/rules scripts.
WARNING
dpatch is deprecated, please switch to the `3.0 (quilt)' Debian source package format instead. See http://wiki.debian.org/Projects/Deb-
Src3.0#FAQ for a short guide on how to do it.
USAGE
Using dpatch.make is rather straightforward: one has to include the file in debian/rules, change the appropriate targets to depend on patch
and unpatch, and that is all it takes.
Figuring out what the appropriate target is, requires some thought. Generally, one has a build target, or config.status, or configure (or
any of these with a -stamp suffix). Most of the time these are called first during the build, so one of these (the one that exists, and is
not depended upon by another one) has to be modified to depend on the patch target in dpatch.make.
Doing the same for the clean target is easier. One only has to rename the old rule to, say, clean-patched, then make a new one that has
clean-patched and unpatch in its list of prerequisites.
CUSTOMISATION
There are a few variables which are used by dpatch.make, which can be set before including it, in order to change the systems behaviour a
little.
These variables are:
DEB_SOURCE_PACKAGE
This is the name of the source package, used when creating the stamp file. By default, it is empty.
DPATCH_STAMPDIR
This is the directory where stamp files will be put. Default is debian/patched.
DPATCH_STAMPFN
The name of the stamp file, which contains the patch descriptions and other possible meta-data. Default value is patch-stamp.
DPATCH_PREDEPS
A list of make targets to call before applying the dpatch.
DPATCH_WORKDIR
The target directory to apply patches to. By default, it is the current directory.
PATCHLIST
The list of patches to apply. This is an alternative to debian/patches/00list - that is, if this variable is not empty, the
contents of 00list will be ignored, and this variable will be used instead.
EXAMPLE
include /usr/share/dpatch/dpatch.make
build: build-stamp
build-stamp: patch-stamp
${MAKE}
touch build-stamp
clean: clean1 unpatch
clean1:
${MAKE} clean
rm -rf debian/files debian/substvars debian/imaginary-package
.PHONY: patch unpatch ...
.
.
.
SIDE EFFECTS
Using dpatch.make instead of calling dpatch directly has one side effect: it will create a file called patch-stamp containing some
meta-information extracted from the scriptlets.
Depending on a phony patch target directly from build target may cause build target to be reevaluated even when there is no change to be
done. Instead, try making build-stamp depend on patch-stamp as specified in this example.
AUTHOR
Originally by Gergely Nagy. Modified by Junichi Uekawa.
SEE ALSO
dpatch(1), dpatch(7), dpatch-edit-patch(1), dpatch-list-patch(1), dpatch-convert-diffgz(1)
DPATCH 2 Dec 13 2011 DPATCH.MAKE(7)