Sponsored Content
Full Discussion: how to run a killed process
Operating Systems Solaris how to run a killed process Post 302339231 by jim mcnamara on Thursday 30th of July 2009 05:33:39 AM
Old 07-30-2009
Does the function have a signal handler? That will stop some kill commands - but not all signals are trappable.

One way is to run a script from crontab periodically to check for the presence of the daemon, and rerun it if it has been bumped off.

Normally daemons are run from a protected account, one that only root can su to for example. This stops random acts of aggression against your daemon.
 

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. UNIX for Dummies Questions & Answers

Who is the parent of a killed process ?

Suppose we have the following process tree: init-> ProcessA->processB->processC then I kill processB Who is the parent of the processC? init or the processA (6 Replies)
Discussion started by: Puntino
6 Replies

3. Programming

how to delay a process from getting killed

We are forking a process B from process A and the process B should display the details it reads from process C(daemon process) continuously. Let us say that the process C sents 100 packets.The process B receives all the 100 packets from the process C before it prints all details of 31... (1 Reply)
Discussion started by: cijkmysj
1 Replies

4. Shell Programming and Scripting

Sybase Process Killed - How to identify

I have this shell script and in case the sybase process is been killed how can identify whether the process was killed or not, as the error code always returns 0. #!/bin/sh isql -S SERVER -U user -P pass<<TOP select * from tableName go TOP echo $? (2 Replies)
Discussion started by: dinjo_jo
2 Replies

5. Solaris

LDAP process getting killed

Hi all, Currently I am using LDAP to store some network related data, When I run following script ./ns-slapd ldif2db Execution of above script terminates displaying "Killed" on the console. As far as I know, a process can be killed by two ways- 1. manually running " kill -9 <PID of LDAP... (1 Reply)
Discussion started by: akash_mahakode
1 Replies

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

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

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

9. Shell Programming and Scripting

how to prevent process from being killed

Hi,all.Well,I know someone has already asked this question before,however,It's too long before.So i post a new thread here. Here is the issue.I have a shell script that use awk to calculate something and the script takes about 15 mins,it will use 100% CPU,and the system automatically killed the... (2 Replies)
Discussion started by: homeboy
2 Replies

10. Shell Programming and Scripting

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. adm 1522... (1 Reply)
Discussion started by: murali1687
1 Replies
rdc(1M) 																   rdc(1M)

NAME
rdc - user interface for Routing Administration Manager (RAMD) SYNOPSIS
coresize] filesize] seconds] DESCRIPTION
provides a user-oriented interface for working with the and routing daemons. and are referred to as routing daemons. provides a command- line interface to start and stop these daemons. In addition, it provides commands to check the configuration file for syntax errors, make the daemon dump core, and dump the current state of the daemon. can reliably determine the running state of the routing protocols. This can be used in shell scripts to manipulate Options supports the following command-line options: Specifies that does not change the kernel forwarding table while running and routing daemons. This option is useful to test the daemons, when the daemons should operate as a route server that does not forward. Suppresses the stderr messages of and routing daemons. This option can be used to suppress informational messages that are normally printed to the standard output, and the log error messages through syslogd(1M). Specifies the time in seconds for which waits to start, stop, reconfigure and terminate daemons. By default, this value is set to 10 seconds. Specifies the maximum size of a core dump produced by the routing daemons invoked using Specifies the maximum size of a file produced or created by the routing daemons invoked using Commands The following commands are used to send HP-UX signals to or routing daemons for various purposes: Sends an abort signal to the requested daemon and terminates the daemon with a core dump. The core files are generated in the file where can be or Sends a signal to the requested daemon to dump its current state into the where is one of the routing daemons. Kills the daemon abruptly. This command is used when the daemon hangs. Sends signal to the requested daemon to reread its configuration file and reconfigure its current state. Sends signal to the requested daemon to terminate gracefully. Sends signal to the daemon to toggle the trace. If tracing is enabled, this command causes tracing to be suspended and the trace file to be closed. If tracing is disabled, the trace file is reopened and tracing initiated. This is useful to move the trace files. If or the routing daemon tracing is modified using this command and the daemons are reconfigured with the trace options, the effect on tracing is with respect to the configuration file. Sends signal to to recheck the interface configuration. periodically checks the kernel interface configuration for any changes. This command can be used to force the daemon to check the interface status immediately. Currently, the only valid argument for this com- mand is for checking on By default, obtains its configuration information from the file. maintains many versions of the configuration file. The versions of the configuration file maintained by are as follows: command of is used to create this configuration file. When must install a new configuration file using the command, the existing file is renamed as file. When creates a new configuration file, using the command, the existing file is renamed as and the existing is renamed as file. Configuration File Commands The following commands perform operations related to configuration files: Checks for syntax errors. This is done after changes are made to the configuration file and before reconfiguring the routing daemons. The system administrator use this command to ensure that there are no syntax errors in the configuration file, which can otherwise terminate the daemons on reconfiguration. Checks the file for syntax errors. Renames the file to retaining the older versions of the configuration files. This operation fails if does not exist. Replaces the old configuration file to This command fails, if the file does not exist or if the file is of zero length, or if the backout command deletes an existing, non-zero length file. Performs a operation even if the file exists and is of non-zero length. Sets all configuration files to mode 664, owner root and group trusted non-root user. This allows a trusted non-root user to modify the configuration files. Creates a new configuration file, with zero length. The file mode is set to 664, owner root and group trusted non-root user. This allows a trusted non-root user to install a new configuration file. Controlling Daemons The following commands can be used to control the daemons: Starts The command returns an error if is already running. It invokes and waits for the time period specified with option. A non-zero exit status is returned, if an error is detected while executing the binary, or if a lock is not obtained on the pid file within the speci- fied wait time. Starting invokes all the configured protocols in the configuration file of The following commands can be used to determine the current state of the daemon or to stop or restart and other IPv6 routing protocols. Determines if daemons are currently running. exits with a zero status if the daemon is running and with a non-zero value if the daemons are not running. Stops the requested routing daemon gracefully. Stopping stops all the daemons. Restarts the requested daemon. reports an error, if there is a failure. EXAMPLES
To start type the following at the HP-UX command prompt: If successful, the pid of the daemon is displayed. To get the current state of the daemons, type the following at command prompt: This will dump the current state of the and routing daemons. The dump files for the and routing daemons are and respectively; where is one of the routing daemons. To reconfigure the routing daemons, change the configuration file and issue the following command at the command prompt: AUTHOR
was developed by Future software Ltd. FILES
where, can be or the routing daemons. SEE ALSO
kill(1), ram_monitor(1M), ramd(1M), syslogd(1M), signal(2), ramd.conf(4). rdc(1M)
All times are GMT -4. The time now is 05:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy