10-12-2002
time dd if=/dev/zero of=bigfile bs=1024 count=500000
will time creation of a 500MB file on just about any unix.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i have to delete some files that were created on a particular date. is there any way to do that without affecting the files that were modified on the same date? (1 Reply)
Discussion started by: sskb
1 Replies
2. Shell Programming and Scripting
IS there any command to find the file creation time in Unix. (2 Replies)
Discussion started by: tinivt
2 Replies
3. Shell Programming and Scripting
I have a very big file of 5gb size and there are about 50 million records in there. I have to delete the records based on recrord number that I know fromoutside with out opening the file. The record numbers are very random like 5000678, 7890005 etc.
Can somebody let me know how i can... (5 Replies)
Discussion started by: dsravan
5 Replies
4. Programming
Hi Everybody,
Is their any functions to find out the file creation time in 'C' (2 Replies)
Discussion started by: mr_manii
2 Replies
5. Shell Programming and Scripting
Hi All,
Cany any one help me in solving this..
Problem statement: I have a requirement to find the time from which there are no files created in a given directory. For this I am assuming that I need to get the file creation time in seconds, then the current time in seconds using `date +%s`.... (7 Replies)
Discussion started by: chary
7 Replies
6. Shell Programming and Scripting
Hello folks,
I have a file, but it change every seconds, i use stats command to check its creation time, but it shows access,modify and change time same. Is there any other way to see the file creation date/time?
Thanks (2 Replies)
Discussion started by: learnbash
2 Replies
7. Solaris
Hi,
There are servers SERVER1 and SERVER2. Both have Sun Solaris 5.1 operating system . A binary file called "Runme" is running in SERVER1 without any issues. But same binary file " Runme" creates core file while exiting . Both operating systems have similar setups. What would be the reason for... (1 Reply)
Discussion started by: joe.mani
1 Replies
8. Red Hat
Hi Everybody,
I would like to know file creation date and time in linux. I went throgh google and forums got some information but from that i am not sure for my question. Please check the following information.
"ls -l" ==> but it is just gives the last modified time and date of the file.... (2 Replies)
Discussion started by: mastansaheb
2 Replies
9. UNIX for Dummies Questions & Answers
Hi All,
Can any one help how to long list today's files in unix.i.e files which are have been created today should be able to "ls -ltr" .I should be able to apply the "ls -ltr" command on today's files(should not include all the files which were there in the directory).
Thanks in advance!!! (3 Replies)
Discussion started by: Balasankar
3 Replies
10. Shell Programming and Scripting
Hi ,
In a folder I have multiple files. I want total time taken to write those files. Can you please suggest what will be the best way to go for it? (2 Replies)
Discussion started by: Anupam_Halder
2 Replies
KILL(1) Linux User's Manual KILL(1)
NAME
kill - send a signal to a process
SYNOPSIS
kill [ -signal | -s signal ] pid ...
kill [ -L | -V, --version ]
kill -l [ signal ]
DESCRIPTION
The default signal for kill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP,
CONT, and 0. Alternate signals may be specified in three ways: -9 -SIGKILL -KILL. Negative PID values may be used to choose whole process
groups; see the PGID column in ps command output. A PID of -1 is special; it indicates all processes except the kill process itself and
init.
SIGNALS
The signals listed below may be available for use with kill. When known constant, numbers and default behavior are shown.
Name Num Action Description
0 0 n/a exit code indicates if a signal may be sent
ALRM 14 exit
HUP 1 exit
INT 2 exit
KILL 9 exit cannot be blocked
PIPE 13 exit
POLL exit
PROF exit
TERM 15 exit
USR1 exit
USR2 exit
VTALRM exit
STKFLT exit might not be implemented
PWR ignore might exit on some systems
WINCH ignore
CHLD ignore
URG ignore
TSTP stop might interact with the shell
TTIN stop might interact with the shell
TTOU stop might interact with the shell
STOP stop cannot be blocked
CONT restart continue if stopped, otherwise ignore
ABRT 6 core
FPE 8 core
ILL 4 core
QUIT 3 core
SEGV 11 core
TRAP 5 core
SYS core might not be implemented
EMT core might not be implemented
BUS core core dump might fail
XCPU core core dump might fail
XFSZ core core dump might fail
NOTES
Your shell (command line interpreter) may have a built-in kill command. You may need to run the command described here as /bin/kill to
solve the conflict.
EXAMPLES
kill -9 -1
Kill all processes you can kill.
kill -l 11
Translate number 11 into a signal name.
kill -L
List the available signal choices in a nice table.
kill 123 543 2341 3453
Send the default signal, SIGTERM, to all those processes.
SEE ALSO
pkill(1), skill(1), kill(2), renice(1), nice(1), signal(7), killall(1).
STANDARDS
This command meets appropriate standards. The -L flag is Linux-specific.
AUTHOR
Albert Cahalan <albert@users.sf.net> wrote kill in 1999 to replace a bsdutils one that was not standards compliant. The util-linux one
might also work correctly.
Please send bug reports to <procps-feedback@lists.sf.net>
Linux November 21, 1999 KILL(1)