But what about a process started as nohup process and detached from controlling terminal ?
It has no terminal attached, I don't think it can be called as a daemon.
Started as a nohup or not doesn't matter. Most well written daemons will explicitly ignore signals that they want to ignore and install handlers for signals that they want to receive.
But if it's detached from it's controlling terminal, it is a daemon. This is exactly what happens when you restart cron or inetd from the command line. Since you don't think that processes with no controlling terminals are daemons, what is your definition of a daemon?
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)
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)
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)
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)
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)
Hi,
When process listing, I came across a process running as user daemon.
daemon 23576 23574 0 07:32:04 ? 0:07 oracle (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
root 27526 27444 1 07:38:43 ttyp5 0:00 grep 23574
why a process runs as user daemon, when it should be... (3 Replies)
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
LEARN ABOUT OSF1
lsmsad
lsmsad(8) System Manager's Manual lsmsad(8)NAME
lsmsad - Starts the Storage Administrator (SA) daemon
SYNOPSIS
/usr/sbin/lsmsad
DESCRIPTION
The SA daemon, lsmsad, is a process required by lsmsa, the SA graphical user interface (GUI). The daemon issues commands and obtains system
information on behalf of SA.
The SA daemon runs on a Tru64 UNIX system on which LSM is initialized and running. The SA client runs on any machine that supports the
Java Runtime Environment.
The SA daemon is automatically started at boot time. Under normal conditions, the daemon does not need to be run manually.
If SA does not start during the boot process, enter:
/sbin/init.d/lsmsa stop
To restart SA, enter:
/sbin/init.d/lsmsa start
Only one SA daemon can be running on a system at a given time. If a second SA daemon attempts to start, it will fail.
RESTRICTIONS
You must be root user to run lsmsad.
FILES
The script that starts lsmsad at boot time. The command log file that tracks SA tasks. The access log file that tracks login to SA. The
server log file that tracks server startup information and server errors. The log maintenance shell script that saves and compresses log
files.
SEE ALSO lsmsa(8), volintro(8)lsmsad(8)