Sponsored Content
Full Discussion: printing trailing dot
Top Forums Shell Programming and Scripting printing trailing dot Post 302354781 by vidyadhar85 on Saturday 19th of September 2009 06:40:32 PM
Old 09-19-2009
which OS??
In AIX kill -9 won't give such error
and simply kill means
Quote:
To stop a given process, enter:

kill 1095

This stops process 1095 by sending it the default SIGTERM signal. Note that process 1095 might not actually stop if it has made special
arrangements to ignore or override the SIGTERM signal.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Printing Problems in unix ... ( Bar-cdoe - Ip Printing)

Hi guys ... i need ur help with some printing problem in unix ... first prob. : i wanna print from my NCR unix to an Win NT , Ip based printing server ( HP JetDirect ) . My issue , is it possible to print directly to an Ip address from unix ? How do i make it work to get any results ?... (3 Replies)
Discussion started by: QuickSilver
3 Replies

2. Shell Programming and Scripting

dot files

Hi, everyone. I'm now using rsync command, and please tell me what is the wildcard for below looks like. I want to chose dotfiles, such as .ipod .apple but i don't want to chose . and .. ------------------ .* doesn't work, of course. Thanks, Euler04 (2 Replies)
Discussion started by: Euler04
2 Replies

3. Linux

Regarding Dot Matrix Printing

Hi all, What I want is that can we manage printing a text file on a Dot Matrix printer installed on a Linux machine and the printer should not take the normal A4 format, but should print only to the extent the text file has text in it. What happen usually is that when we give print comand to any... (0 Replies)
Discussion started by: aman_mlt
0 Replies

4. Shell Programming and Scripting

Remove trailing G

Hello, I am trying to write a script that will calculate the amount of data remaining in a storage volume. I'm running Tru64 Unix version 5.1B patch kit 6. The script is being run against an AdvFS domain. I am programming in Korn Shell version M-11/16/88f. The basic idea is that I want to run df... (3 Replies)
Discussion started by: Heathe_Kyle
3 Replies

5. UNIX for Dummies Questions & Answers

Solaris mail routing to Windows SMTP server (trailing dot)

Hello, Firstly, appologies, i am a windows man but i'm picking things up really quickly.! We have some Unix boxes on our estate that route mail to a Windows SMTP server. This doesn't seem to work and after looking at the message headers it looks like the mail is getting bounced. :( -----... (4 Replies)
Discussion started by: M2TTJ
4 Replies

6. UNIX for Dummies Questions & Answers

variable name with dot(.)

Hi, Is it possible to declare variable with name having dot(.) in it ? something like gs.test='HELLO' Thanks in advance :) (1 Reply)
Discussion started by: gopalss
1 Replies

7. Windows & DOS: Issues & Discussions

Linux to Windows Printing: PDF starts printing from middle of page.

We are using Red Hat. We have a issue like this: We want to print from Linux, to a printer attached to a Windows machine. What we want to print is a PDF. It prints, but the printing starts from the middle of the page. In the report, there is no space at the top but still printing starts from the... (5 Replies)
Discussion started by: rohan69
5 Replies

8. UNIX for Dummies Questions & Answers

Sco Unix printing : jobs hangs in queue - printing via lp versus hpnpf

Hi, We have a Unix 3.2v5.0.5. I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts). This is the configuration file : Code: root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies

9. Shell Programming and Scripting

Mv or cp with a . (dot)?

How can I rename a file with a . prefix? I actually need to copy the file but the . seems to be very tough to do. mv ./bla ../fa/la/.bla - doesn't work. I've tried all sorts of bracketing and that doesn't work. Maybe the only way to do it would be to name the file _.bla then rename it... (19 Replies)
Discussion started by: scribling
19 Replies
kill(1) 						      General Commands Manual							   kill(1)

NAME
kill - Sends a signal to a running process SYNOPSIS
kill -l [exit_status] kill [-signal_name | signal_number] process_ID... kill -s signal_name process_ID... Note The C shell has a built-in version of the kill command. If you are using the C shell, and want to guarantee that you are using the command described here, you must specify the full path /usr/bin/kill. See the csh(1) reference page for a description of the built-in command. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: kill: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
The kill command supports the following options: Lists signal names. If you specify an exit status (a numeric value) or the shell special parameter $?, which expands to the exit status of the most recent pipeline, kill prints the name of the terminating signal. Specifies the signal to send, using one of the symbolic names defined for required signals or job control signals. Values of signal_name are recognized in both uppercase or lowercase letters, and without the SIG prefix. The symbolic name 0 (zero), which represents the value 0 (zero), is also recognized. The corresponding signal is sent instead of SIGTERM. Specifies the signal to send to the process. You can specify either a name, stripped of the SIG prefix (such as KILL), or a number (such as 9). For information about signal names and numbers, see the sigaction() system call. OPERANDS
A process identification number [Tru64 UNIX] There are several special process identification numbers (PIDs) that you can specify to cause the following special actions: The signal is sent to all processes having a process group ID equal to the process group ID of the sender, except those with a process ID of 0 (zero) and the process ID of the init process. If the effective user ID of the sender is not 0 (root), the signal is sent to all processes with a process group ID equal to the effective user ID of the sender, except those with a process ID of 0 (zero) and the process ID of the init process. If the effective user ID of the sender is 0 (root), the signal is sent to all processes, except the process ID of 0 (zero) and the process ID of the init process. The signal is sent to all processes whose process group number is equal to the absolute value of PID. Note that when you specify any negative PID, you must also specify the signal to be sent, even the default signal SIGTERM. A decimal integer specifying a signal number or the exit status of a process terminated by a signal. DESCRIPTION
The kill command sends a signal to one or more running processes. The default is the SIGTERM signal (signal number 15), which usually ter- minates processes that do not ignore or catch the signal. You identify the process to be signaled by specifying its process identification number (also known as the process ID or PID). The shell displays the PID of each process that is running in the background or, if you start more than one process in a pipeline, the shell displays the number of the last process. You can also use the ps command to display PIDs. [Tru64 UNIX] The name of the kill command is misleading because many signals, including SIGUSR1, do not terminate processes. [Tru64 UNIX] Unless you are operating with superuser privileges, the process you wish to signal must belong to you. When operating with superuser authority, you can signal any process. [Tru64 UNIX] See the kill() system call for a complete discussion of kill. Note that the csh command contains a built-in subcommand named kill, but the command and subcommand do not necessarily work in the same way. For information on the subcommand, see csh. NOTES
Some applications and scripts depend on the process ID of the init program being 1 (one): do not depend on it. Instead, use standard methods, such as the ps and grep commands, to obtain all process IDs. EXIT STATUS
The following exit values are returned: At least one matching process was found, and the specified signal was successfully processed for at least one matching process. An error occurred. EXAMPLES
The following command terminates the process with the specified PID: kill 1095 This command terminates process 1095 by sending it the default SIGTERM signal. Note that process 1095 might not actually terminate if it has made special arrangements to ignore or catch the SIGTERM signal. The following command terminates several processes that ignore the default signal: kill -KILL 17285 15692 This command sends SIGKILL to processes 17285 and 15692. The SIGKILL signal usually cannot be ignored or caught. The following com- mand terminates all of your background processes: kill 0 This command sends the SIGTERM signal to all members of the shell process group. This includes all background processes started with &. Although the signal is sent to the shell, it has no effect because the shell ignores the default signal 15. The following com- mand terminates all of your processes and logs you out: kill -KILL 0 This command sends SIGKILL to all members of the shell process group. Because the shell cannot ignore SIGKILL, this also terminates the login shell and logs you out. If you are using multiple windows, this closes the active window. The following command terminate all the processes that you own: kill -KILL -1 This command sends SIGKILL to all the processes that you own, even those that belong to other process groups. If you are using mul- tiple windows, this command closes all the windows. The following command sends a specific signal to a specific process: kill -USR1 1103 This command sends the SIGUSR1 signal to process 1103. The action taken on the SIGUSR1 signal is defined by the particular applica- tion you are running. The following command lists the signal names in numerical order, stripped of the SIG prefix: kill -l 1) HUP 13) PIPE 25) XFSZ 37) RTMIN+4 2) INT 14) ALRM 26) VTALRM 38) RTMIN+5 3) QUIT 15) TERM 27) PROF 39) RTMIN+6 4) ILL 16) URG 28) WINCH 40) RTMIN+7 5) TRAP 17) STOP 29) PWR 41) RTMAX-7 6) LOST 18) TSTP 30) USR1 42) RTMAX-6 7) EMT 19) CONT 31) USR2 43) RTMAX-5 8) FPE 20) CHLD 32) RESV 44) RTMAX-4 9) KILL 21) TTIN 33) RTMIN 45) RTMAX-3 10) BUS 22) TTOU 34) RTMIN+1 46) RTMAX-2 11) SEGV 23) POLL 35) RTMIN+2 47) RTMAX-1 12) SYS 24) XCPU 36) RTMIN+3 48) RTMAX The command output can vary from system to system. ENVIRONMENT VARIABLES
The following environment variables affect the execution of kill: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. FILES
Specifies signal names. SEE ALSO
Commands: csh(1), killall(8), ksh(1), ps(1), Bourne shell sh(1b), POSIX shell sh(1p) Functions: kill(2), sigaction(2) Standards: standards(5) kill(1)
All times are GMT -4. The time now is 05:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy