01-17-2002
If the daemon process is still sending text to the o/p , i think u can direct the o/p of the daemon
process to /dev/null and i think it shouldn't
be a problem
10 More Discussions You Might Find Interesting
1. 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
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
LEARN ABOUT HPUX
fclose_unlo
fclose(3S) fclose(3S)
NAME
fclose(), fflush(), fclose_unlocked(), fflush_unlocked() - close or flush a stream
SYNOPSIS
Obsolescent Interfaces
DESCRIPTION
causes any buffered data for the named stream to be written out, and the stream to be closed. Buffers allocated by the standard input/out-
put system may be freed.
is performed automatically for all open files upon calling exit(2).
If stream points to an output stream or an update stream in which the most recent operation was output, causes any buffered data for the
stream to be written to that file; otherwise any buffered data is discarded. The stream remains open.
If stream is a null pointer, performs this flushing action on all currently open streams.
Obsolescent Interfaces
and close or flush a stream.
RETURN VALUE
Upon successful completion, and return 0. Otherwise, they return EOF and set to indicate the error.
ERRORS
If or fails, is set to one of:
The flag is set for the file descriptor underlying stream and the process would be delayed in the write operation.
The file descriptor underlying
stream is not valid.
An attempt was made to write a file
that exceeds the process's file size limit or the maximum file size (see ulimit(2)).
or was interrupted by a signal.
The process is in a background process group
and is attempting to write to its controlling terminal, is set, the process is neither ignoring nor blocking the signal,
and the process group of the process is orphaned.
There was no free space remaining on the device containing the file.
An attempt was made to write to a pipe
that is not open for reading by any process. A signal is also sent to the process.
Additional values may be set by the underlying and functions (see write(2), lseek(2) and close(2)).
WARNINGS
and are obsolescent interfaces supported only for compatibility with existing DCE applications. New multithreaded applications should use
and
SEE ALSO
close(2), exit(2), lseek(2), write(2), flockfile(3S), fopen(3S), setbuf(3S), thread_safety(5).
STANDARDS CONFORMANCE
fclose(3S)