Unix pkill error; does wily obstruct me killing the process? Post: 302569369

Sponsored Content

Special Forums UNIX and Linux Applications Unix pkill error; does wily obstruct me killing the process? Post 302569369 by nerdogan551 on Monday 31st of October 2011 05:01:16 AM

10-31-2011

Registered User

Unix pkill error; does wily obstruct me killing the process?

have two scripts on Unix; one that starts some processes and the other one for killing a process. At first, I ran the .sh without WILY in it and it worked perfectly; in this way, I could also ran my stopper process. However I need WILY in this so I added it to my script but this time, a message about WILY shows up instead of the first version which is perfectly normal but when I try to run my stop process it doesn't work anymore; it probably couldn't find the process with the name given. Here are my scripts:

start_scpc.sh

Code:

export CLASSPATH='.:'
    export CLASSPATH=$CLASSPATH'./resources'

    cd lib
    for file in *.jar; do export CLASSPATH=$CLASSPATH':./lib/'$file; done
    cd ..


    # --- define WILY java options here :: Must be declared at the beginning
    ## ------------------------------------------------------------------------------
    WILY_HOME="/export/home/scpcstb/wily823"
    WILY_OPTIONS="-javaagent:${WILY_HOME}/Agent.jar -Dcom.wily.introscope.agentProfile=${WILY_HOME}/IntroscopeAgent.profile -Dcom.wily.introscope.agent.agentName=SCPC_STB"
    ## ------------------------------------------------------------------------------


    APPLICATION_NAME=SCPC_STB
    MAIN='tr.com.turkcellteknoloji.scpc.core.Main'
    JAVA_PARAM="-Xmx1g -Xbatch  -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=5563 -Dcom.sun.management.jmxremote.authenticate=false  -Dcom.sun.management.jmxremote.ssl=false"

    echo "JVM"
    echo "CHECKING $APPLICATION_NAME PROCESS"

    if [ 0 == `pgrep -fl application=$APPLICATION_NAME | wc -l` ]
    then
      echo "....................STARTING $APPLICATION_NAME........................"
      echo "Please wait"
      echo "See log files for details"

    /usr/jdks/scpcstb/bin/java -server ${WILY_OPTIONS} -Dapplication=$APPLICATION_NAME $JAVA_PARAM -cp $CLASSPATH $MAIN >> ./logs/scpcConsole.log 2>&1  &


    sleep 1    
    until [ 0 != `pgrep -fl application=$APPLICATION_NAME | wc -l` ]; do
    sleep 1
    done

    echo "....................$APPLICATION_NAME STARTED........................."

    else
    echo "$APPLICATION_NAME IS ALREADY RUNING!!!"
    fi

    exit 1

and my stop_scpc.sh:

Code:

pkill -f application=SCPC_STB

This pkill doesn't work anymore... Any help with this would be highly appreciated, thanks.

nerdogan551

View Public Profile for nerdogan551

Find all posts by nerdogan551

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

killing unix job after the job process completes

Hi, Thanks in advance. i need to kill a unix background running job after that job process completes. i can kill a job by giving the following unix command kill -9 processid how to kill the job after the current process run gets completed ? Appreciate your valuable help. ...

2. Solaris

killing a unix job after the job process gets completed

3. UNIX for Dummies Questions & Answers

killing a process

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

4. Shell Programming and Scripting

Killing of a process and send a mail if the process doesnot come up within 2 minutes

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...

5. UNIX for Dummies Questions & Answers

killing the process

Hi, First, I am running a scipt.While the script is running I realize that I dont want the script to be run so I am killing the script externally.Before the process gets terminated or killed it should delete all the temporary files created by the script.How to do this?Can anyone help me? ...

6. UNIX for Dummies Questions & Answers

kill/pkill process by CMD info.

I have a process that I'd like to kill. Doing a "ps -fu myusername" gives me: UID PID PPID C STIME TTY TIME CMD myusername 5443 1 0 10:05 ? 00:00:00 /bin/sh /some/path/crap.sh -s /yet/another/path/parentProcess myusername 5593 5443 0 ...

7. Shell Programming and Scripting

Killing a process within 5 min it starts in Unix using perl

Hi All, I have to kill a program whose pid, i will be getting. Multiple processes will be getting started by my script of same kind in a series. So for after each call to a process i need to write a command or script which can kill the process if it takes more than 5min. In this i will...

8. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

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...

9. Homework & Coursework Questions

Unix Script -- To Skip killing a specific process

Hi, By using ps -aux | awk '/mine/{split($15,a,"/");print $1,$2,a}' i get the below listed PID's with there corresponding processes. adm 1522 ABC_Process.tra adm 1939 GENE_Process.tra adm 2729 GENE_Archive.tra adm 3259 xyz_Process.tra I use ps -aux | awk...

10. Red Hat

Process with S state(Interruptable) in RHEL and gives Advertise error after restarting/Killing the p

Hello, In our Production system one process is in S state(interruptible)and after killing and restarting the process gives 'advertise error'. This error goes after rebooting the Server. I have RHEL 5.9 (tikanga) OS in our server. We tried debugging the issue with the help of 'strace' command...

LEARN ABOUT HPUX

systemd.kill

SYSTEMD.KILL(5) 						   systemd.kill 						   SYSTEMD.KILL(5)

NAME

       systemd.kill - Process killing procedure configuration

SYNOPSIS

       service.service, socket.socket, mount.mount, swap.swap, scope.scope

DESCRIPTION

       Unit configuration files for services, sockets, mount points, swap devices and scopes share a subset of configuration options which define
       the killing procedure of processes belonging to the unit.

       This man page lists the configuration options shared by these five unit types. See systemd.unit(5) for the common options shared by all
       unit configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5) and systemd.scope(5) for more
       information on the configuration file options specific to each unit type.

       The kill procedure configuration options are configured in the [Service], [Socket], [Mount] or [Swap] section, depending on the unit type.

OPTIONS

       KillMode=
	   Specifies how processes of this unit shall be killed. One of control-group, process, mixed, none.

	   If set to control-group, all remaining processes in the control group of this unit will be killed on unit stop (for services: after the
	   stop command is executed, as configured with ExecStop=). If set to process, only the main process itself is killed. If set to mixed,
	   the SIGTERM signal (see below) is sent to the main process while the subsequent SIGKILL signal (see below) is sent to all remaining
	   processes of the unit's control group. If set to none, no process is killed. In this case, only the stop command will be executed on
	   unit stop, but no process be killed otherwise. Processes remaining alive after stop are left in their control group and the control
	   group continues to exist after stop unless it is empty.

	   Processes will first be terminated via SIGTERM (unless the signal to send is changed via KillSignal=). Optionally, this is immediately
	   followed by a SIGHUP (if enabled with SendSIGHUP=). If then, after a delay (configured via the TimeoutStopSec= option), processes still
	   remain, the termination request is repeated with the SIGKILL signal (unless this is disabled via the SendSIGKILL= option). See kill(2)
	   for more information.

	   Defaults to control-group.

       KillSignal=
	   Specifies which signal to use when killing a service. This controls the signal that is sent as first step of shutting down a unit (see
	   above), and is usually followed by SIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to SIGTERM.

	   Note that, right after sending the signal specified in this setting, systemd will always send SIGCONT, to ensure that even suspended
	   tasks can be terminated cleanly.

       SendSIGHUP=
	   Specifies whether to send SIGHUP to remaining processes immediately after sending the signal configured with KillSignal=. This is
	   useful to indicate to shells and shell-like programs that their connection has been severed. Takes a boolean value. Defaults to "no".

       SendSIGKILL=
	   Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the
	   service around. Takes a boolean value. Defaults to "yes".

SEE ALSO

       systemd(1), systemctl(1), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
       systemd.exec(5), systemd.directives(7), kill(2), signal(7)

systemd 237															   SYSTEMD.KILL(5)