Defining Custom Signal Post: 302338595

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Defining Variables

I'm trying to define a variable named sin I already have a variable named cos, which has the value "hello" I want sin to have the value of "hellothere", so sin would be something like sin = $cos & "there" but I'm not sure that I know the syntax. Can anyone help? :confused:

2. AIX

defining a printer in qconfig

I've got a modified samba script (named it winprint) that I can use to print out to a to a shared Win Network printer from an AIX machine. This is a modification of the samba provided smbprint script changed to work under AIX as the backend for a queue. It does not read a config file I can print...

3. Shell Programming and Scripting

defining variables

Hey all, I was wondering if someone would take a look at this script I'm working on. I don't know if i have the syntax correct for my variables and if the for loop is written correctly. any assistance would be greatly appreciated. #!/usr/bin/bash ###########################################...

4. UNIX and Linux Applications

Problems with defining triggers

I am running the example from the following webpage: MySQL :: MySQL 5.0 Reference Manual :: 12.1.11 CREATE TRIGGER Syntax and the problem is that triggers cannot be defined for some reason: CREATE DATABASE IF NOT EXISTS triggertest; USE triggertest; CREATE TABLE test1(a1 INT); CREATE TABLE...

5. Programming

Defining the inputStream object

Question regarding extend issue What is the reason behind defining the inputStream object in this way... InputStream inputStream = new FileInputStream("c:\\input.txt"); I know that FileInputStream extends InputStream, is there anything else ? I mean we could have define it like ...

6. UNIX for Dummies Questions & Answers

defining variable in .profile

In root dir i have created a .profile file and added variable and assigned a path to it: a = '/dir/dir' export a but when i echo (echo $a) the path or use this variable the value or path not getting displayed. i tried executing the .profile and logging out and logging in, didnt workout. am...

7. UNIX for Dummies Questions & Answers

Defining an alias FreeBSD

I have defined this alias as quick way to find out which mount point to use for a USB drive after inserting it: # alias da='dmesg | grep da | grep MB' However, when invoking it, it states the following: # da da: Command not found. Can someone explain what is the issue here and how it can be...

8. UNIX for Dummies Questions & Answers

Help with defining PATH

Hi All, I have a trivial question but I dont know how to solve it. So basically I'm working on a USB key and I have a directory with some scripts which I use to work on files present in other directories within the USB or sometimes on the main harddisk too. The problem is every time I have to...

9. Programming

Problem defining a struct

I have the following code and getting the compilation errors baseLib/DynBaseObj.h:80: error: expected constructor, destructor, or type conversion before �(' token baseLib/DynBaseObj.h:89: error: expected constructor, destructor, or type conversion before �(' token baseLib/DynBaseObj.h:101:...

10. UNIX for Dummies Questions & Answers

Defining variable problem

Hi I'd say I'm having this weird problem where my script isn't taking the value off a variable or printing it. My code is like this: set count_C= `grep -c C mols` set count_H= `grep -c H mols` set count_O= `grep -c O mols` sed -i '7,7 s/$/ $count_C $count_O $count_H/g' input It...

LEARN ABOUT REDHAT

kill

KILL(1) 						     Linux Programmer's Manual							   KILL(1)

NAME

       kill - terminate a process

SYNOPSIS

       kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
       kill -l [ signal ]

DESCRIPTION

       The command kill sends the specified signal to the specified process or process group.  If no signal is specified, the TERM signal is sent.
       The TERM signal will kill processes which do not catch this signal.  For other processes, it may be necessary to use the KILL  (9)  signal,
       since this signal cannot be caught.

       Most  modern  shells  have  a  builtin  kill function, with a usage rather similar to that of the command described here. The `-a' and `-p'
       options, and the possibility to specify pids by command name is a local extension.

OPTIONS

       pid... Specify the list of processes that kill should signal.  Each pid can be one of five things:

	      n      where n is larger than 0.	The process with pid n will be signaled.

	      0      All processes in the current process group are signaled.

	      -1     All processes with pid larger than 1 will be signaled.

	      -n     where n is larger than 1.	All processes in process group n are signaled.	When an argument of the form `-n' is given, and it
		     is  meant	to  denote  a process group, either the signal must be specified first, or the argument must be preceded by a `--'
		     option, otherwise it will be taken as the signal to send.

	      commandname
		     All processes invoked using that name will be signaled.

       -s signal
	      Specify the signal to send.  The signal may be given as a signal name or number.

       -l     Print a list of signal names.  These are found in /usr/include/linux/signal.h

       -a     Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.

       -p     Specify that kill should only print the process id (pid) of the named processes, and not send any signals.

SEE ALSO

       bash(1), tcsh(1), kill(2), sigvec(2), signal(7)

AUTHOR

       Taken from BSD 4.4.  The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.

Linux Utilities 						  14 October 1994							   KILL(1)