I have many Debian and they all work fine except 2 of them. It is kernel related I think.
Here is a list of some of the kernels working fine (they are all Debian distribution kernels):
2.06.26-2-686
2.06.32-5-686
2.06.32-5-amd64
3.02.00-4-686-pae
3.02.00-4-amd64
3.16.00-4-amd64
Here are the 2 kernels that do NOT work as I wish (they are OVH Dedicated Server Debian custom kernel):
2.06.21.05-grsec-xxxx-grs-ipv4-32
3.14.32-xxxx-grs-ipv6-64
Unfortunately, I failed to upgrade the kernel because (according to the hosting company), the hardware is incompatible.
I can live with a non standard kernel but if anyone knows where I can tweak the setting that makes other users processes invisible, I'd take some help with great gratitude.
I wasn't sure if I should post it here of in the Shell Script category, but I figured it was definitely a newbie question.
I'm trying to write a script that will check for the existence of a specific file (or for any files within the directory) and then take specific actions. I've removed all... (2 Replies)
Hey all,
I have total new with shell scripting so I don't know if what I need to do even possible, here it is...for a duration of time (say...1 hour) I need to check for the existence of a particular file, if it exists then I will invoke a java program or I will continue to check until a)... (2 Replies)
Hello,
I have this process app.fcgi and a directory containing images. I'd like to ensure that only app.cgi can access those images and more generally that folder.Thanks! (1 Reply)
Hi
I want to check a particular file is available or not. But i know only the pattern of that file sat AB1234*.txt.I need the latest file name and it ll be used in the script. How can i do this using ls -ltr command.
Thanks,
LathishSundar V (2 Replies)
Hi,
I want to make a bash script which is running like :
1.sh http://www. google.com
and check if the url does exist printing a message.
I want to save the source code of this page in a file.
Could you help me ? (4 Replies)
Hi
I'm using the below command in shell script to check for file exists in the path
if
.....
fi
path and test are variables
path and the file exists but the commands inside if condition is executed (! operator used)
Is the above way of checking for file existence is correct?
... (4 Replies)
Hope someone can help me on this
In a directory ,files are dynamically generated.I need a script to do the following
if files are not received for more than 2 hours or if the received file is empty
then do something
How can I put that in a script.Thank you
eg. in cd /dir_name the... (13 Replies)
I'm on AIX. I have triggered an infinite loop process (to keep looking for input file availability for further process). At present only I can kill the process.
In case my colleague wants to kill the process for any reason, how do I provide permission to others to kill the process?
Currently... (3 Replies)
Discussion started by: krishmaths
3 Replies
LEARN ABOUT BSD
kill
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)