01-04-2011
Thanks for the suggestion, I have already tried this but fail to run the application on Linux machine with plink from windows machine.
As I explained above, there is no problem in running daemon and application (child of daemon) on Linux machine. Problem is there when I am trying to run the daemon on Linux machine from windows machine(remote machine) with plink. I mean on windows command prompt executing the following command:
plink -ssh -pw <password> <machine IP>:/ "path"; ./daemon
This command will establish the connection with Linux machine and will execute daemon process present in the given path. This command is launching the daemon process on Linux machine but after 1-2 sec, daemon is stopping the execution. I am not able to find out the reason that causing the problem
7 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. 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. Red Hat
After i launch the process as back ground, when I try to grab the shell by sending the enter, process is going to Stopped state.
How do I successfully run the job in bg with &.
Thanks in Advance (1 Reply)
Discussion started by: hansini
1 Replies
5. Programming
Hi all
I have a program in C++ that I compiled on Ubuntu 9.0 and Centos 5, after I got it running on Windows. In this program, I show progress of a process using the following construct:
i = 0;
quantum = floor(total_iterations, 100);
perc = 0;
do
{
remain = fmod(i, quantum);
... (3 Replies)
Discussion started by: msaqib
3 Replies
6. UNIX for Advanced & Expert Users
Hi all,
Normally to launch a process in the remote machine I will use ssh to the machine and launch the process.I want to launch the remote machine process with out login into the machine . Is there any way.
It may be any workaround method.
Thanks in advance .:) (3 Replies)
Discussion started by: karthigayan
3 Replies
7. 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
LEARN ABOUT CENTOS
wd_keepalive
WD_KEEPALIVE(8) System Manager's Manual WD_KEEPALIVE(8)
NAME
wd_keepalive - a simplified software watchdog daemon
SYNOPSIS
wd_keepalive [-c filename|--config-file filename]
DESCRIPTION
This is a simplified version of the watchdog daemon. If configured so it only opens
.IR /dev/watchdog , and keeps writing to it often enough to keep the kernel from resetting, at least once per minute. Each write delays
the reboot time another minute. After a minute of inactivity the watchdog hardware will cause a reset. In the case of the software watchdog
the ability to reboot will depend on the state of the machines and interrupts.
The wd_keepalive daemon can be stopped without causing a reboot if the device /dev/watchdog is closed correctly, unless your kernel is com-
piled with the CONFIG_WATCHDOG_NOWAYOUT option enabled.
Under high system load wd_keepalive might be swapped out of memory and may fail to make it back in in time. Under these circumstances the
Linux kernel will reset the machine. To make sure you won't get unnecessary reboots make sure you have the variable realtime set to yes in
the configuration file watchdog.conf. This adds real time support to wd_keepalive: it will lock itself into memory and there should be no
problem even under the highest of loads.
On system running out of memory the kernel will try to free enough memory by killing process. The wd_keepalive daemon itself is exempted
from this so-called out-of-memory killer.
OPTIONS
Available command line options are the following:
-c config-file, --config-file config-file
Use config-file as the configuration file instead of the default /etc/watchdog.conf.
FILES
/dev/watchdog
The watchdog device.
/var/run/wd_keepalive.pid
The pid file of the running wd_keepalive.
SEE ALSO
watchdog.conf(5)
watchdog(8)
4th Berkeley Distribution January 2005 WD_KEEPALIVE(8)