Sponsored Content
Top Forums Shell Programming and Scripting Capturing the killed process logs Post 302696457 by murali1687 on Wednesday 5th of September 2012 04:10:36 AM
Old 09-05-2012
Capturing the killed process logs

I have two set of questions.
1) To skip killing some process automatically.

2) To kill other process and capture their log.

I have set of process, some needs to be killed gracefully and others should be skipped.

Listed are the process.
Code:
 
adm 1522 ABC_DE-BillingAgreement-2012-07-11-Agreement.tra
adm 1939 ABC_DE-GenesisHTTPandSOAPAdapter-2012-05-19-Genesis_Process.tra
adm 2729 ABC_DE-SpecialKenan-2012-05-17-Kenan_Archive.tra

adm 2729 ABC_DE-Gracefull-2012-05-17-Grace-Process.tra 
adm 2729 ABC_DE-Peacefull-2012-05-17-Peace-Process.tra


To Skip killing some process :
====================
From the above listed process first 3 process should not be killed, and others should be killed gracefully.
For which i have the below script. Can any one tell me if it works (or) needs any modifications.
Code:
grep -v -E "BillingAgreement | GenesisHTTPandSOAPAdapter | SpecialKenan" inputfile | cut -d" " -f2 | xargs kill

To capture the logs of other killed processes:
==============================
Logs are located in "/var/prod/logs" directory as
Code:
ABC_DE-Gracefull-2012-05-17-Grace-Process.log
ABC_DE-Peacefull-2012-05-17-Peace-Process.log

The killed processes get re-started automatically.
Once the process are killed,they logs will read as "stopped" and once re-started it reads as "started"
Example:
Code:
ENGINE-002 Engine  ABC_DE-Gracefull-2012-05-17-Grace-Process stopped
ENGINE-002 Engine  ABC_DE-Gracefull-2012-05-17-Grace-Process started

ENGINE-001 Engine  ABC_DE-Peacefull-2012-05-17-Peace-Process stopped
ENGINE-001 Engine  ABC_DE-Peacefull-2012-05-17-Peace-Process started

How can i capture these logs once they have stopped (or) started.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

process not getting killed

I have a process that is in the sleeping state "S" and I have tried to stop it with a run control script that I use to stop/start it - but it does not stop. I have tried kill -9 <PID of process> with no change. I imagine that this process is sleeping with the kernel. It does not respond to... (5 Replies)
Discussion started by: finster
5 Replies

2. Solaris

how to run a killed process

hi, i am creating a daemon process for updating the file at regular interval.one problem with this is if anybody kills the daemon it wont update the file.anybody have idea how to rerun the daemon if it killed.the code is written in c++ in solaries environment. thnaks & regards suresh (8 Replies)
Discussion started by: suresh_rtp
8 Replies

3. UNIX for Dummies Questions & Answers

SAS Process Getting Killed

HI all, I am very new to AIX (matter of fact Unix). We are currently automating out manual process using Unix Shell Scripting. My wrote a shell script which will accept the name of the sas job as parameter, checks the existense of the sas file in the specified folder. If it is not present,... (1 Reply)
Discussion started by: anubhav2020
1 Replies

4. UNIX for Dummies Questions & Answers

Protect a Process from Being Killed

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

5. Shell Programming and Scripting

Capturing FTP logs

Hi Guys, I am trying to capture the FTP Logs in a log file. I am using the below code. ftp -d -n -v $Remote_Host << EOD > $Ftp_LOG; Since iam running the script in debug mode, i am able to see that the ftp is done and the file has been transferred. But the log file does not have... (7 Replies)
Discussion started by: mac4rfree
7 Replies

6. UNIX for Dummies Questions & Answers

Process Killed : Need to find why ?

Hi reader, I'm making a tool out of korn shell script that is running on a HP-UX server. But everytime i invoke the tool, it gets killed after a while (mid-process). I have tried re-running it a couple of times but each invocation ending up the same way .. following is a snippet of the o/p... (8 Replies)
Discussion started by: clakkad
8 Replies

7. Emergency UNIX and Linux Support

Capturing console (/dev/ttyS1) logs

Hi, I have been trying to capture console logs from the init script. When the ramfs is mounted, i check if usb is connected , if conncted, i mount it and redirected the console logs like so: cat & /dev/ttyS1 >> /mnt/logs.txt I'm getting /bin/sh : /dev/ttyS1 :permission denied ... (8 Replies)
Discussion started by: xerox
8 Replies

8. Shell Programming and Scripting

Help in capturing Time from Autosys Logs

Hi Guys, I'm very new to Shell scripting and have to design a code which I'm not able to find a way to. I will try to explain the aim in detail and shall be obliged if anyone could help me with the coding snippet. I have an input file who's every row has a few details about an autosys Job. I shall... (0 Replies)
Discussion started by: Crusnik02
0 Replies

9. UNIX for Beginners Questions & Answers

Help with Capturing time from Autosys logs

Hi Guys, I'm very new to Shell scripting and have to design a code which I'm not able to find a way to. I will try to explain the aim in detail and shall be obliged if anyone could help me with the coding snippet. I have an input file who's every row has a few details about an autosys Job. I shall... (1 Reply)
Discussion started by: Crusnik02
1 Replies

10. Shell Programming and Scripting

Shell script for capturing FTP logs

I have a script #!/bin/bash HOST=ftp.example.com USER=ftpuser PASSWORD=P@ssw0rd ftp -inv $HOST <<EOF user $USER $PASSWORD cd /path/to/file mput *.html bye EOF the script executes sucessfully I need to capture the FTP logs to a logfile should contain FTP Login successful ... (1 Reply)
Discussion started by: rajeshas83
1 Replies
ps(1B)						     SunOS/BSD Compatibility Package Commands						    ps(1B)

NAME
ps - display the status of current processes SYNOPSIS
/usr/ucb/ps [-aceglnrSuUvwx] [-t term] [num] DESCRIPTION
The ps command displays information about processes. Normally, only those processes that are running with your effective user ID and are attached to a controlling terminal (see termio(7I)) are shown. Additional categories of processes can be added to the display using vari- ous options. In particular, the -a option allows you to include processes that are not owned by you (that do not have your user ID), and the -x option allows you to include processes without controlling terminals. When you specify both -a and -x, you get processes owned by anyone, with or without a controlling terminal. The -r option restricts the list of processes printed to running and runnable processes. ps displays in tabular form the process ID, under PID; the controlling terminal (if any), under TT; the cpu time used by the process so far, including both user and system time, under TIME; the state of the process, under S; and finally, an indication of the COMMAND that is running. The state is given by a single letter from the following: O Process is running on a processor. S Sleeping. Process is waiting for an event to complete. R Runnable. Process is on run queue. Z Zombie state. Process terminated and parent not waiting. T Traced. Process stopped by a signal because parent is tracing it. OPTIONS
The following options must all be combined to form the first argument: -a Includes information about processes owned by others. -c Displays the command name rather than the command arguments. -e Displays the environment as well as the arguments to the command. -g Displays all processes. Without this option, ps only prints interesting processes. Processes are deemed to be uninteresting if they are process group leaders. This normally eliminates top-level command interpreters and processes waiting for users to login on free terminals. -l Displays a long listing, with fields F, PPID, CP, PRI, NI, SZ, RSS, and WCHAN as described below. -n Produces numerical output for some fields. In a user listing, the USER field is replaced by a UID field. -r Restricts output to running and runnable processes. -S Displays accumulated CPU time used by this process and all of its reaped children. -t term Lists only process data associated with the terminal, term. Terminal identifiers may be specified in one of two forms: the device's file name (for example, tty04 or term/14 ) or, if the device's file name starts with tty, just the digit identifier (for example, 04). -u Displays user-oriented output. This includes fields USER, %CPU, %MEM, SZ, RSS, and START as described below. -U Obsolete. This option no longer has any effect. It causes ps to exit without printing the process listing. -v Displays a version of the output containing virtual memory. This includes fields SIZE, %CPU, %MEM, and RSS, described below. -w Uses a wide output format, that is, 132 columns rather than 80. If the option letter is repeated, that is, -ww, this option uses arbitrarily wide output. This information is used to decide how much of long commands to print. Note: The wide output option can be viewed only by a superuser or the user who owns the process. -x Includes processes with no controlling terminal. num A process number may be given, in which case the output is restricted to that process. This option must be supplied last. DISPLAY FORMATS
Fields that are not common to all output formats: USER Name of the owner of the process. %CPU CPU use of the process. This is a decaying average over up to a minute of previous (real) time. NI Process scheduling increment (see getpriority(3C) and nice(3UCB)). SIZE The total size of the process in virtual memory, including all mapped files and devices, in kilobyte units. SZ Same as SIZE. RSS Real memory (resident set) size of the process, in kilobyte units. UID Numerical user-ID of process owner. PPID Numerical ID of parent of process. CP Short-term CPU utilization factor (used in scheduling). PRI The priority of the process (higher numbers mean lower priority). START The starting time of the process, given in hours, minutes, and seconds. A process begun more than 24 hours before the ps inquiry is executed is given in months and days. WCHAN The address of an event for which the process is sleeping (if blank, the process is running). %MEM The ratio of the process's resident set size to the physical memory on the machine, expressed as a percentage. F Flags (hexadecimal and additive) associated with the process. These flags are available for historical purposes; no meaning should be currently ascribed to them. A process that has exited and has a parent, but has not yet been waited for by the parent, is marked <defunct>; otherwise, ps tries to determine the command name and arguments given when the process was created by examining the user block. FILES
/dev/tty* /etc/passwd UID information supplier ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscpu | +-----------------------------+-----------------------------+ SEE ALSO
kill(1), ps(1), whodo(1M), getpriority(3C), nice(3UCB), proc(4), attributes(5), termio(7I) NOTES
Things can change while ps is running. The picture ps gives is only a close approximation to the current state. Some data printed for defunct processes is irrelevant. SunOS 5.11 26 May 2006 ps(1B)
All times are GMT -4. The time now is 06:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy