Recently our FreeBSD 7.1 i386 system became very sluggish.
Nothing much is happening over there & whatever is running takes eternity to complete.
All the troubleshooting hinted towards a very high nice percentage.
Can that be the culprit?
Pasting snippets of top command, please advice whether it's a cause of concern & what are the possible remedies. Idle percentage mentions 0.
Thanks for the support.
Last edited by Scrutinizer; 04-07-2014 at 03:17 AM..
Reason: code tags
Hi,
I've got some CPU bottleneck on a HP-UX 11 server : i didn't
understand it until i discover i've got an unusual high percentage
of NICE% CPU regarding my DBRMS process (Sybase 12.x).
How do i have to understand it and how to resolve it ?
Thx. (0 Replies)
Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command... (2 Replies)
hello everybody:
I have some job running on tru64 system and Im the root, due to limited resources I end up with my job ( vdump) for example taking the lowest share, I researched the nice command on the net, but couldnt get enough info, can I use it to already running process or I only use it... (1 Reply)
Hi,
I have two identical 12 CPU HPUX machines, and I run the same processes on each that load the boxes fully.
top on one reports activity under the NICE (19%) and SYS (18%) columns, while top on the other reports 0% NICE and 16% SYS. What would cause NICE to be zero on one machine and not... (5 Replies)
Hi, new here and need some help. Sometimes my site is extremely slow, if when there aren't too many people on, whereas when there are over 300 online members the site may be very fast. We use CentOS, PHP 5.26. The server has 4GB and Plesk usually shows about 2 or 3 GB free.
I believe I can see... (4 Replies)
Hello,
Some guy said to me that using the nice command to decrease the priority of a process is a myth, that the operating system corrects the priorities as the processes need cpu. Is this true? (4 Replies)
Hello folks,
I am searching for pattern, after that i want its presenece on top to bottom basis, like
cat abcd.txt |grep "123"|awk {'print $3'} |sort|uniq -c
it show result like
10 1.1.1.1
1 1.1.1.1
15 1.1.1.1
100 1.1.1.1
but i want to see this like
100 1.1.1.1
15 1.1.1.44
10... (3 Replies)
Running 2 VM Guests on an HPUX Integrity Server. One Guest runs great, the other is always at a high NICE value and 0% idle as shown in TOP:
What do you think should be tuned to bring down the NICE and increase IDLE %? Thanks in advance
-hpuxadmin
slow VM GUEST
Load averages: 2.56,... (5 Replies)
Dear Friends,
I have a directory when i take du of that directory it takes alot of memory and cpu and I/O, i want to use nice to run my script that have du command slowly so it won't take I/O and cpu, please suggest. (6 Replies)
Discussion started by: learnbash
6 Replies
LEARN ABOUT FREEBSD
style.makefile
STYLE.MAKEFILE(5) BSD File Formats Manual STYLE.MAKEFILE(5)NAME
style.Makefile -- FreeBSD Makefile file style guide
DESCRIPTION
This file specifies the preferred style for makefiles in the FreeBSD source tree.
o All makefiles should have an SCM ID at the start of the file, followed by a blank line.
# $FreeBSD$
o .PATH: comes next if needed, and is spelled ``.PATH: '', with a single ASCII space after a colon. Do not use the VPATH variable.
o Special variables (i.e., LIB, SRCS, MLINKS, etc.) are listed in order of ``product'', then building and installing a binary. Special
variables may also be listed in ``build'' order: i.e., ones for the primary program (or library) first. The general ``product'' order
is: PROG/[SH]LIB/SCRIPTS FILES LINKS [NO_]MAN MLINKS INCS SRCS WARNS CFLAGS DPADD LDADD. The general ``build'' order is:
PROG/[SH]LIB/SCRIPTS SRCS WARNS CFLAGS DPADD LDADD INCS FILES LINKS [NO_]MAN MLINKS.
o Omit SRCS when using <bsd.prog.mk> and there is a single source file named the same as the PROG.
o Omit MAN when using <bsd.prog.mk> and the manual page is named the same as the PROG, and is in section 1.
o All variable assignments are spelled ``VAR='', i.e., no space between the variable name and the =. Keep values sorted alphabetically, if
possible.
o Do not use += to set variables that are only set once (or to set variables for the first time).
o Do not use vertical whitespace in simple makefiles, but do use it to group locally related things in more complex/longer ones.
o WARNS comes before CFLAGS, as it is basically a CFLAGS modifier. It comes before CFLAGS rather than after CFLAGS so it does not get lost
in a sea of CFLAGS statements as WARNS is an important thing. The usage of WARNS is spelled ``WARNS?= '', so that it may be overridden
on the command line or in make.conf(5).
o ``NO_WERROR= yes'' should not be used, it defeats the purpose of WARNS. It should only be used on the command line and in special cir-
cumstances.
o CFLAGS is spelled ``CFLAGS+= ''.
o Listing -D's before -I's in CFLAGS is preferred for alphabetical ordering and to make -D's easier to see. The -D's often affect condi-
tional compilation, and -I's tend to be quite long. Split long CFLAGS settings between the -D's and -I's.
o Do not use GCCisms (such as -g and -Wall) in CFLAGS.
o Typically, there is one ASCII tab between VAR= and the value in order to start the value in column 9. An ASCII space is allowed for
variable names that extend beyond column 9. A lack of whitespace is also allowed for very long variable names.
o .include <bsd.*.mk> goes last.
o Do not use anachronisms like $< and $@. Instead use ${.IMPSRC} or ${.ALLSRC} and ${.TARGET}.
o To not build the ``foo'' part of the base system, use NO_FOO, not NOFOO.
o To optionally build something in the base system, spell the knob WITH_FOO not WANT_FOO or USE_FOO. The latter are reserved for the
FreeBSD Ports Collection.
o For variables that are only checked with defined(), do not provide any fake value.
The desire to express a logical grouping often means not obeying some of the above.
EXAMPLES
The simplest program Makefile is:
# $FreeBSD$
PROG= foo
.include <bsd.prog.mk>
The simplest library Makefile is:
# $FreeBSD$
LIB= foo
SHLIB_MAJOR= 1
MAN= libfoo.3
SRCS= foo.c
.include <bsd.lib.mk>
SEE ALSO make(1), make.conf(5), style(9)HISTORY
This manual page is inspired from the same source as style(9) manual page in FreeBSD.
BUGS
There are few hard and fast style rules here. The style of many things is too dependent on the context of the whole makefile, or the lines
surrounding it.
BSD January 8, 2005 BSD