Dear Group,
I am not much used to UNIX. The company I am hosting wiht refuses to help me with this trouble, but as near as I can see, it is NOT my trouble.
I have had this service for over a year. I just renewed for another year and all of a sudden the disk quota has been disappearing. I... (3 Replies)
Hello
I run Gentoo Linux on my computer:
Athlon XP 1700+ ~1,46 mhz
512 mb ram
After a while, my computer works really slow, and when I cat /proc/meminfo, I see that I only have 8mb of 512 mb free!
How is that possible?
I dont run anything I can think of that eats that amount of... (4 Replies)
after a long period of running, the network application's CPU load in our syst em increase slowly, the failed at the end. we use "truss" tool to trace the process, found that it processes something like "semop" ,"semctl","thread_waitlock","kread" kernel call . The trace log file looks like the... (0 Replies)
Dear all,
I have a pro c application running in the unix environement.
This pro c program actually trigger by a java application from sun workstation.
Recently, when we released a new proc c application and notice that the application occupying the CPU resources even through we check that the... (1 Reply)
Hi!
Could someone explain me why the below code is printing the contents of IF block 5 times instead of 0?
#!/bin/bash
VAR1="something"
VAR2="something"
for((i=0;i<10;i++))
do
if(($VAR1=~$VAR2))
then
echo VAR1: $VAR1
echo... (3 Replies)
Hi,
may be this is an AIX noob question:
my current C++ application runs on Linux and is quite memory consuming. Therefore, the application writes a logfile after it has finished containing memory information, CPU information, information on the running other processes besides my application... (0 Replies)
Hi all,
using AWK iam sorting auniq data from a file the file size is 8GB, while running that script , the over all cpu usage will be nearly 8
how to avoid this ?? any other alternate is available for awk?
Thanks in Advance
Anish kumar.V (13 Replies)
Hi All ,
I am trying to pull out below things from AIX machine (any type)
1. number of physical processor
2. number of logical processsors
3. Total number of processors (physical plus logical)
4. total number of cores
5. list of installed applications with versions and vendor name
... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies
LEARN ABOUT NETBSD
kill
KILL(1) BSD General Commands Manual KILL(1)NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the process(es) specified by the pid operand(s).
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
Display the name of the signal corresponding to exit_status. exit_status may be the exit status of a command killed by a signal (see
the special sh(1) parameter '?') or a signal number.
If no operand is given, display the names of all the signals.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following pids have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
0 Broadcast the signal to all processes in the current process group belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill argu-
ments. See csh(1) for details.
SEE ALSO csh(1), pgrep(1), pkill(1), ps(1), kill(2), sigaction(2), signal(7)STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 6 AT&T UNIX.
BSD April 28, 1995 BSD