Hi all
I am getting a repeated message in the /var/log/messages log.
Oct 23 10:52:00 hostname xinetd: refused connect from xxx.yyy.zz.aa
Oct 23 10:57:26 hostname xinetd: refused connect from xxx.yyy.zz.aa
The IP is pretty much the same. The last part of the IP has changes a few times making... (1 Reply)
I have an application which has a lot of cout & cerr statements.
This application also opens a log file (for eg a.log).
When this application is run from the inittab file as follows
/bin/sh -c " . /etc/timezone; exec /test"
all the cout & cerr statements are printed in the log file... (1 Reply)
Hello Everyone,
I have an option for users in my shell script to create log file. So if user saying “yes” on it, I'm redirecting all output to log file by doing this: > /output.log. However I would like the output being displayed on the screen at the same time. Is it possible? If yes, does anybody... (2 Replies)
I tried to redirect the find command to a file (using find ..... > asdf ) and the file asdf is always empty . The results keep appearing on the screen.
Is there another way to do this ?
hmm . i just figured out that the file is empty only when in fact all results of the find command give a... (1 Reply)
Hi all,
I have a c++ program which is running fine but has some printfs which its spews on to the screen, which I need for debugging.
But, I execute this program through a java, i.e I run a java program which actually launches my c++ executable and when it does this, I see none of my printfs... (1 Reply)
I have to confirm that an engine was not able to run. In the output below you see that it indeed got errors, but it didn't send those messages to the output file. When I run the same thing with a different executable it works. So does this mean something in the executable could cause it not to... (7 Replies)
Good afternoon,
I'm have program that executes in background another programs. The main program would be programA and the programs executed by the main one, would be program1a, program1b and program1c.
I need the programs to continue the execution no matter if the shell connection is lost,... (6 Replies)
Hi. recently in many of our lpars we are getting a message in errpt as "C6ACA566 0315094014 U S dtc MESSAGE REDIRECTED FROM SYSLOG".
I have also checked the /etc/syslog.conf file. It doesn't point to error log.
Can someone please advise about how to fix this error ?
pmut3:/> errpt -aj... (4 Replies)
Hi
echo " username "
read username
echo "password"
stty -echo
read password
stty echo
through read i am taking standard input and redirecign them to a file
echo " username=${username}/${password} " > file.lst
now from the same shell script i want to delete the password (i.e... (4 Replies)
Discussion started by: rosheks
4 Replies
LEARN ABOUT NETBSD
daemon
DAEMON(3) BSD Library Functions Manual DAEMON(3)NAME
daemon -- run in the background
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <stdlib.h>
int
daemon(int nochdir, int noclose);
DESCRIPTION
The daemon() function is for programs wishing to detach themselves from the controlling terminal and run in the background as system daemons.
Unless the argument nochdir is non-zero, daemon() changes the current working directory to the root (/).
Unless the argument noclose is non-zero, daemon() will redirect standard input, standard output and standard error to /dev/null.
RETURN VALUES
On return 0 indicates success with -1 indicating error.
ERRORS
The function daemon() may fail and set errno for any of the errors specified for the library functions fork(2) and setsid(2).
SEE ALSO fork(2), setsid(2)HISTORY
The daemon() function first appeared in 4.4BSD.
CAVEATS
Unless the noclose argument is non-zero, daemon() will close the first three file descriptors and redirect them to /dev/null. Normally,
these correspond to standard input, standard output and standard error. However, if any of those file descriptors refer to something else
they will still be closed, resulting in incorrect behavior of the calling program. This can happen if any of standard input, standard output
or standard error have been closed before the program was run. Programs using daemon() should therefore make sure to either call daemon()
before opening any files or sockets or, alternately, verifying that any file descriptors obtained have a value greater than 2.
BUGS
daemon() uses fork() as part of its tty detachment mechanism. Consequently the process id changes when daemon() is invoked. Processes
employing daemon() can not be reliably waited upon until daemon() has been invoked.
BSD September 3, 1999 BSD