12-01-2009
FWIW - lsnctrl starts a daemon.
There are errors that can occur after the parent process is detached/defunct and can no longer report an error. This is a common issue with a daemon starter script/program.
I would not expect a return code of failure except in the instance where you request, for example, a duplicate daemon instance. Most daemon drivers are coded to barf at the the very beginning in that case.
The daemon can fail independently and not report anything to the calling process when there are system errors, or there is a subsequent network error. That's why you have to scan logs rather than check return codes. IMO.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have the below script I am running on a Solaris system to check the status of a Tivoli Workload Scheduler job and return the status. We need this script to return a '0' if any of the jobs in the stream are in a "EXEC" state and an "1" if in a "HOLD" state. I am not a programmer so I am not sure... (1 Reply)
Discussion started by: leezer1204
1 Replies
2. UNIX for Dummies Questions & Answers
Suppose I have a script which is monitoring a directory
whenever a file drops in that directory,it sends alert
say I want to write a return code for the above script
which on successful execution of script gives a return value
Based on return code , I want to do initiate some jobs in other... (1 Reply)
Discussion started by: abhib45
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Can anyone tell me if there are return codes for SFTP? If so how would you capture them? I've tried 'man sftp' but its not particularly helpful.
Many thanks
Helen :confused: (4 Replies)
Discussion started by: Bab00shka
4 Replies
4. UNIX for Advanced & Expert Users
I have a simple script which renames a file.How do i capture the return code of the script if the script fails (3 Replies)
Discussion started by: kris01752
3 Replies
5. HP-UX
Can any body please tell me the return codes of RDIST tool?
I am using RDIST (through an UNIX script) to synchronize files between two servers say ukblx151(source) & ukapx050(target).
RDIST raises an alert mail (through notify option) in case of success & also failure but there is a problem if... (0 Replies)
Discussion started by: vishal_ranjan
0 Replies
6. Shell Programming and Scripting
Hi
In an unix script I am using an Perl one liner perl -i -ne '-----'
If the perl one liner fails i am not able to catch the return code.
It always give 0 as return code. Can you tell me how can i catch the return code
perl -i -ne '---'
RETCODE=$?
echo $RETCODE
Thanks and Regards
Ammu (2 Replies)
Discussion started by: ammu
2 Replies
7. UNIX for Dummies Questions & Answers
This is a high-level explanation, if more details are needed, please do not hesitate to ask.
I have a set of .ctl files which I want to execute:
AV1.ctl
AV2.ctl
AV3.ctl
I have a script which has a for loop in it:
for filename in AV1 AV2 AV3
do
. execute_another_script.sh
done
... (2 Replies)
Discussion started by: hern14
2 Replies
8. Shell Programming and Scripting
sftp -v b $putlist $SFTP_ID@TARGET_SERVER
How can I get a return code if fails to put the file?
sftp -v b $getlist $SFTP_ID@TARGET_SERVER
How can I get a return code if fails to put the file? (1 Reply)
Discussion started by: TimHortons
1 Replies
9. Shell Programming and Scripting
Hi,
I wanted to know the significance of different return codes when we do echo $?
I know when $? returns 0 the command has worked successfully.
but what does $? = 1, 2, 3 etc. signify.
Thanks in advance for the help !!! (3 Replies)
Discussion started by: aarti.popi
3 Replies
10. UNIX for Dummies Questions & Answers
Not sure if this is of any use but......
I was messing around with getting return codes greater than 255 for special usage...
Of course the code could be made simple but in this code the new stored return code
is generated as exit is progressing...
#!/bin/sh
# Real and imaginary return... (9 Replies)
Discussion started by: wisecracker
9 Replies
LEARN ABOUT FREEBSD
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
The daemon() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate
the error.
ERRORS
The daemon() function 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), sigaction(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 out-
put, or standard error have been closed before the program was run. Programs using daemon() should therefore either call daemon() before
opening any files or sockets, or verify that any file descriptors obtained have values greater than 2.
The daemon() function temporarily ignores SIGHUP while calling setsid(2) to prevent a parent session group leader's calls to fork(2) and then
_exit(2) from prematurely terminating the child process.
BSD
June 9, 1993 BSD