08-21-2006
daemon process
how i will write the daemon process,if any body have sample daemon process send me.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I have to write a daemon process, which performs certain operations in the background.
Now since it performs operations in the background, it should not display anything to the standard output.
The problem is that it still displays, text on standard output.
Can anyone tell me (it is... (2 Replies)
Discussion started by: s_chordia
2 Replies
2. Programming
This is gonna seem really silly to almost evryone here - but I need to know :
what is a daemon process?
Thanks (6 Replies)
Discussion started by: Kanu77
6 Replies
3. UNIX for Advanced & Expert Users
My daemon process is the child of init and init has the responsibility to remove it, once it turns zombie. But I want to ask why the daemon process which is child of init turns zombie in the first place. What measures I have to take to avoid this?
rish (1 Reply)
Discussion started by: rish2005
1 Replies
4. Shell Programming and Scripting
Hello,
I need to run a command on remote Linux using the ssh command from my local machine. I am able to execute the command on remote machine using ssh but it's behaving strangely.
The command is supposed to start a daemon process on remote linux box and the control should return back to me... (5 Replies)
Discussion started by: nitinshukla
5 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I am new to this forum and this is my first post here...
I have never worked on either Pro*C or Multithreading..Now, i have to write a Pro*C, Multithreading daemon process.. I dont know where to start.. Can anybody help me with examples?
1. need to write a Pro*C multithreading... (0 Replies)
Discussion started by: kachiraju
0 Replies
6. Programming
I have a scenario where I need to find if a process is a daemon process or not. This check needs to be done from within the process. I know there are no direct API's to do so. I have explored these options.
1. ctermid() - this can be unsuccessful as per the man pages
2. int devtty; if ((devtty... (7 Replies)
Discussion started by: vino
7 Replies
7. Shell Programming and Scripting
Dear Unix Gurus,
Plz provide major diff between background process and daemon process.
Is it control available for daemon process?. (3 Replies)
Discussion started by: kkl
3 Replies
8. UNIX for Advanced & Expert Users
Hi All,
I am facing problem in launching a application with the help of a daemon process. Actually the application is based on command line that reads various commands for controlling the application from the console and accordingly executes those commands. The application always interact with... (3 Replies)
Discussion started by: gopallinux
3 Replies
9. Shell Programming and Scripting
Hi,
HI ,
I have a simple script that moves files from one folder to another folder, I have already done the open-ssh server settings and the script is working fine and is able to transfer the files from one folder to another but right now I myself execute this script by using my creditianls to... (3 Replies)
Discussion started by: nks342
3 Replies
10. Programming
I wish to make a process run in the background, but only one instance of it, and not many,
so when the program is loaded, it has to check whether another instance of the same
program is running and if so to exit. How do I do this ? (4 Replies)
Discussion started by: sundaresh
4 Replies
vxiod(7) Miscellaneous Information Manual vxiod(7)
NAME
vxiod - Veritas Volume Manager I/O daemon process control device
DESCRIPTION
The vxiod device in Veritas Volume Manager (VxVM) is used to control the number of volume I/O daemons active on the system. A process con-
text is necessary to implement the plex consistency recovery and writeback error handling policies for multi-plex volumes, and for continu-
ing normal I/O after a log write if the volume has logging enabled. It is also required for the plex recovery performed with a mirrored
volume in the read/writeback mode.
There are three aspects of I/O daemon operations:
o General I/O
o Error handling
o Log handling
I/O handling is achieved by an ioctl command that does not return, but instead calls the vxiod routine to wait for errors or I/O requests
and process them. When an error occurs, if there are no I/O daemons active, the I/O simply turns into a failure on that plex. If a gen-
eral I/O request is queued up when no daemons exist, then the I/O will hang forever until a daemon process is created. If I/O daemons are
active, then the I/O is put on a work queue and the daemons are awakened. A daemon takes an error request and tries to read other plexes
until a read succeeds or all plexes have been tried. Then, if the writeback facility is enabled, the daemon tries to write the good data
to each plex that failed on the read. If the write is successful, the read error is nullified. An I/O request is handled in a similar
manner.
Logging is handled in a similar manner. An ioctl command, which does not return, is issued to create a daemon for each volume which has
logging enabled. This daemon monitors two queues: one queue of I/O which was started while the log was busy (the ``log'' queue), and
another queue of requests which have been logged and now need to be started (the ``ready'' queue). I/O requests are taken from the log
queue when the log is no longer busy, and another log write is started. Completion of a log write results in all I/O requests which have
just been logged being placed on the I/O daemon's ready queue where they are immediately started.
One mechanism finds out how many I/O error daemons are running, and another mechanism allows a process to become an I/O daemon. Before a
process becomes an I/O daemon, it should close all open files and detach from the controlling tty. An I/O or logging daemon cannot be
killed except through an explicit ioctl.
FILES
/dev/vx/iod vxiod control device
SEE ALSO
vxiod(1M), ioctl(2)
VxVM 5.0.31.1 24 Mar 2008 vxiod(7)