9 More Discussions You Might Find Interesting
1. Cybersecurity
Hello there,
I would like to protect a Linux system from cloning, I don't mind if the cloned hard drive works in the same computer, but I need to avoid it to work in other one, even if it uses exactly same mainboard model and rest of computer parts. I want the cloned system to get frozen or... (4 Replies)
Discussion started by: Installimat
4 Replies
2. UNIX for Dummies Questions & Answers
Afternoon,
the stat command is used against a file to ascertain date created and last modification time. However a different individual if they so chose could use the touch command to alter the date created or modification time.
Is there anyway to protect against this ?
thanks
Steve (2 Replies)
Discussion started by: sevans29
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have a process which takes 13-15 mins for execution and its getting killed in the meantime.So can you please helpme out how to protect the process from getting killed.
Thanks in advance.
Regards,
Harika (9 Replies)
Discussion started by: harikagrp
9 Replies
4. Cybersecurity
Hi!
Looking for some feed back on this tutorial...
Thank you for checking out this thread.
I'm working on some killer videos right now that will explain in detail how you can protect your website against hackers. The first part of the video series is live right now and it covers Cross-Site... (2 Replies)
Discussion started by: Arne1983
2 Replies
5. UNIX for Dummies Questions & Answers
Hello,
Can someone give me some recommendations on how to protect this account? I understand that this account is an "operator" account and has root access.
Thanks in advance (5 Replies)
Discussion started by: susie2345
5 Replies
6. UNIX for Advanced & Expert Users
We recently had an accidental delete from /. I hold the root password but others are allowed to sudo over to root to perform admin tasks. The only way I want to permit deletion from / is by physically being root (su -).
I'd like to add a line to the sudoers file which would permit all commands... (1 Reply)
Discussion started by: scottsl
1 Replies
7. Shell Programming and Scripting
Hello All,
i work with backup, The below script runs and tar the user specified dir and put it in a backup machine. can any one help me to modify this in such a was that the tar file generated can be given a users specific password so that it can have high security.
KINDLY LET ME... (2 Replies)
Discussion started by: pradeepmacha
2 Replies
8. UNIX for Dummies Questions & Answers
I have created a PHP page that I use to clean files on my machine. I would like to leave the file there but I want to password protect it so that I am the only one that can run it from the shell. Does anyone know how to do this? Thanks.
-Cam (2 Replies)
Discussion started by: perryl7
2 Replies
9. UNIX for Dummies Questions & Answers
we have an hp-ux and a user requested me if i can password protect the dtterm. i know that this is possible but can you give me some hints in making this happen?
thanks :cool: (2 Replies)
Discussion started by: inquirer
2 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
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
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)