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
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
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
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
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
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
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
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
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
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
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
voliod(8) System Manager's Manual voliod(8)
NAME
voliod - Start, stop, and report on Logical Storage Manager kernel daemons
SYNOPSIS
/sbin/voliod
/sbin/voliod [-f] set count
OPTIONS
The following option is used by voliod: Force the kill of the last I/O daemon. Without this option, the I/O daemons can only be reduced to
one.
DESCRIPTION
The voliod utility starts, stops, or reports on Logical Storage Manager I/O daemons. An I/O daemon is a process that provides a process
context for processing any work that needs to be done to process Logical Storage Manager I/O.
When invoked with no arguments, voliod prints the current number of volume I/O daemons on the standard output.
When invoked with the set keyword, the number of daemons specified by count will be created. If more volume I/O daemons exist than are
specified by count, then the excess processes will be terminated. If more than the maximum number are created (currently 64), the requested
number will be silently truncated to that maximum.
The number of daemons to create for general I/O handling depends on system load and usage. One daemon for each CPU on the system is gener-
ally adequate, unless volume recovery seems unusually slow.
Each I/O daemon starts in the background and creates an asynchronously-running kernel thread and becomes a volume I/O daemon. The voliod
utility does not wait for these threads to complete.
NOTES
LSM automatically sets the number of I/O daemons when the system starts, so it is usually not necessary to set or change the number of I/O
daemons with this command.
LSM I/O daemons cannot be killed directly through the use of signals.
The number of Logical Storage Manager I/O daemons currently running can only be determined by running voliod; I/O daemons do not appear in
the list of processes produced by the ps(1) command.
EXIT CODES
The voliod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O error occurs within a spawned
I/O daemon thread, then the I/O is not reflected in the exit status for voliod. Otherwise, voliod returns a nonzero exit status on errors.
Usage errors result in an exit status of 1 and a usage message. If the requested number of daemons cannot be created, then the exit status
is 2, and the number of daemons that were successfully started is reported. If any other error occurs, the exit status is 3.
FILES
The device used to report on and start volume I/O daemon kernel threads.
SEE ALSO
fork(2), volintro(8), vold(8), voldctl(8) ,pthread(8)
voliod(8)