02-27-2002
You're way off the mark. Asking what a daemon does in like asking what a program does....the answer depends on the specific example.
cron, inetd, syslogd all run as daemons and they do a lot. But it is easy to write a daemon that does nothing but just monitor something. It's also easy to write a daemon that does nothing at all.
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. 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
3. Linux
how i will write the daemon process,if any body have sample daemon process send me. (1 Reply)
Discussion started by: suresh_rupineni
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
lockd(8c) lockd(8c)
Name
lockd - network lock daemon
Syntax
/usr/etc/lockd [ -t timeout ] [ -g graceperiod ]
Description
The daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking service
makes this advisory locking support possible by using the system call and the subroutine. The daemon forwards lock requests for remote
data to the server site's lock daemon. The daemon then requests the status monitor daemon, for monitor service. The reply to the lock
request is not sent to the kernel until the status daemon and the server site's lock daemon have replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site daemons to submit reclaim requests. Client site daemons are noti-
fied by of the server recovery and promptly resubmit previously granted lock requests. If a client site's daemon fails to secure previ-
ously granted locks at the server site, the daemon sends the signal SIGLOST to all the processes that were previously holding locks and
cannot reclaim them.
Options
-t timeout The daemon uses timeout (in seconds) as the interval instead of the default value of 15 seconds to retransmit a lock
request to the remote server.
-g graceperiod The daemon uses graceperiod (in seconds) as the grace period duration instead of the default value of 45 seconds.
See Also
fcntl(2), lockf(3), signal(3), statd(8c)
lockd(8c)