Hi,
I need a way to detect the up and down arrow key inputs for my program. I do not want to wait for the return key to be entered(so that rules out getch() and family). Also I need to process several of these inputs in parallel, by servicing each request with a thread.
Is that possible?
... (4 Replies)
Hi,
I am triying to make sure that there exists only one file with the pattern abc* in path /path/. This directory is having many huge files. If there is only one file then I have to take its complete name only to use furter in my script.
I am planning to do like this:
if ; then... (2 Replies)
Dear All,
The sqlplus 'Accept' command is not waiting for user input when I include the command within a shell script.
Note: The 'Accept' command is working fine if I execute it in a SQLPLUS Prompt.
Please fins the below sample script which i tried.
SCRIPT:
--------
#!... (4 Replies)
Hi,
I am trying to send email with attacment and body using "mailx"
(cat body.txt; uuencode attach.txt) | mailx -s "Attachment" abc@xyz.com
When i type this command, the shell is still waiting for me to enter something in standard input and press control D before it sends a mail and... (2 Replies)
Hello,
I have a script that contains the command "whois 1.2.3.4"
Sometimes this command takes far too long to produce any output and as a result the rest of the script is not executed.
Can anyone suggest a method so that if no output is produced after say 2 seconds the script skips that... (2 Replies)
Dear All,
read command not waiting for my input, please suggest.
code:
while read line
do
echo "$line " | grep -i .par$
if ; then
cd ../par
echo " Do you want to proceed"
read
else
cd ../sql
read
fi
done <inp.txt
Its not asking me any input? (2 Replies)
Hi,
I am writing a little script to update a parameters on JMQ. however the JMQ requires a "y" confirmation to be input as part of the cmd I am running. However I want run this script to offline with no input from a user.
it works if a I create a file with with just y in it and pass that in... (3 Replies)
Hi,
I have to create a script (ksh or perl) that starts certain number of parallel jobs (another scripts), each of them runs as a foreground process in a separate session. Plus I start monitoring job that has to determine if any of those scripts is expecting input from operator, and switch to... (4 Replies)
Hi,
i am working on one automation , for that i have writing one shell program that take user input in "while read line" block. but read command is taking value that is readed by While block.
while read line; do
command 1;
command 2
echo -n "Do you want to continute > "
read rsp... (2 Replies)
Discussion started by: ranvijaidba
2 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