I noticed in the mean time, that this is not the case on other systems. Here is the same example from the local computing cluster (which is a CentOS machine - but I am not 100% sure)
I can kill running processes on my linux red hat system using ctrl-c but cannot do it from command line of another terminal using kill -2 pid. Although I can kill them from command line using kill -9 pid and other signals. I would like to do it using the kill -2 pid.
Thanks for your suggestions (6 Replies)
Hi Friends,
I am new to this forum as well as new to shell scripting.
I have a problem here and i need someone to solve this.
Let us consider there are two processes(abc & def).There is a script which kills these two processes(i.e killtheprocess abc). Here abc is the argument .
There is a... (1 Reply)
BASH on Solaris
Hi All,
I posted a problem whereby I was looking to Kill a background (calling Send)mail) process after a certain time had elapsed.
A User Scottn very kindly provided a useful function to do this as below
CheckAndKill()
{
sleep "$EMAIL_TIMEOUT_THEN_KILL"
... (2 Replies)
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
Hi,
I am using net::ftp for transferring files now i am trying in the same Linux server as a result ftp is very fast but if the server is other location (remote) then the file transferred will be time consuming.
So i want try putting FTP part as a background process. I am unaware how to do... (5 Replies)
Hello,
can some please suggest a script, for killing the process PID. This are steps I am currently performing to kill the process.
I cant user service splunk stop, to kill these processes, because of uid and gid mismatch for splunk user.
# service splunk status
Splunk status:
splunkd... (8 Replies)
Hi ,
I have a list of application process id's.
Is there a way to kill all the process listed below using the script, except the once which are starting with " Genesis "
adm 1522 ABC_Process.tra
adm 1939 Genesis_Process.tra
adm 2729 Genesis_Archive.tra
adm 3259 xyz_Process.tra (5 Replies)
I'm pretty sure I had the answer to this months ago and have misplaced it. Needless to say I will bookmark it this time.
I have a background process that's been running way longer than usual. It doesn't output anything to a file, so I can't 'tail -f' it. Is there a command that will enable me to... (2 Replies)
I have a question.
I will be running a background process using nohup and & command at end. I want to send output to a file say myprocess.out.
So will this command work?
nohup myprocess.ksh > myprocess.out &
Thanks in advance guys !!!
:) (3 Replies)
Discussion started by: vx04
3 Replies
LEARN ABOUT DEBIAN
postgresql-common
PG_WRAPPER(1) Debian PostgreSQL infrastructure PG_WRAPPER(1)NAME
pg_wrapper - wrapper for PostgreSQL client commands
SYNOPSIS
client-program [--cluster version/cluster] [...]
(client-program: psql, createdb, dropuser, and all other client programs installed in /usr/lib/postgresql/version/bin).
DESCRIPTION
This program is run only as a link to names which correspond to PostgreSQL programs in /usr/lib/postgresql/version/bin. It determines the
configured cluster and database for the user and calls the appropriate version of the desired program to connect to that cluster and
database, supplying any specified options to that command.
The target cluster is selected by the following means, in descending order of precedence:
1. explicit specification with the --host option
2. explicit specification with the --cluster option
3. if the PGHOST environment variable is set, no further cluster selection is performed. The default PostgreSQL version and port number
(from the command line, the environment variable PGPORT, or default 5432) will be used.
4. explicit specification with the PGCLUSTER environment variable
5. matching entry in ~/.postgresqlrc (see postgresqlrc(5)), if that file exists
6. matching entry in /etc/postgresql-common/user_clusters (see user_clusters(5)), if that file exists
7. If only one local cluster exists, that one will be selected.
8. If several local clusters exist, the one listening on the default port 5432 will be selected.
If none of these rules match, pg_wrapper aborts with an error.
OPTIONS --cluster version/cluster
cluster is either the name of a local cluster, or takes the form host:port for a remote cluster. If port is left empty (i. e. you just
specify host:), it defaults to 5432.
ENVIRONMENT
PGCLUSTER
If $PGCLUSTER is set, its value (of the form version/cluster) specifies the desired cluster, similar to the --cluster option. However,
if --cluster is specified, it overrides the value of $PGCLUSTER.
PG_CLUSTER_CONF_ROOT
This specifies an alternative base directory for cluster configurations. This is usually /etc/postgresql/, but for testing/development
purposes you can change this to point to e. g. your home directory, so that you can use the postgresql-common tools without root
privileges.
FILES
/etc/postgresql-common/user_clusters
stores the default cluster and database for users and groups as set by the administrators.
$HOME/.postgresqlrc
stores defaults set by the user himself.
SEE ALSO user_clusters(5), postgresqlrc(5)AUTHOR
Martin Pitt <mpitt@debian.org>
Debian 2013-01-04 PG_WRAPPER(1)