01-05-2009
I'm not sure ( I didn't look closely at the code), but calling an IO function while handling an IO signal might be a problem. Also, when printing within signals, it's a good idea to call flush().
Also, why would you expect the program to call SIGHUP on itself when exiting? That's only the case if you're connected to a TTY which is closed on you.
9 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
They appear to be turned on, I entered mine in. The check boxes are all checked. And yet, no sigs? (4 Replies)
Discussion started by: l008com
4 Replies
2. UNIX for Dummies Questions & Answers
I am thankful for this site and for the many links provided. I have been going through one of the tutorials, but as I try some things, they don't seem to work.
I am wondering if there is something I need first before being able to use a tutorial (like version number (HP-UX) or how I am getting... (1 Reply)
Discussion started by: arungavali
1 Replies
3. Shell Programming and Scripting
Hi all.
I have a script as below:
cutmth=`TZ=CST+2160 date +%b`
export cutmth
echo $cutmth >> date.log
sed -n "/$cutmth/$p" alert_sbdev1.log > alert_summ.log
My purpose is to run through the alert_sbdev1.log and find the 1st occurence of 'Jan' and send everything after that line to... (4 Replies)
Discussion started by: ahSher
4 Replies
4. Programming
Following code is detecting solaris daytime,when I run it,I can't get any result,code is follows:
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#define BUFFSIZE 150
int main(){
... (2 Replies)
Discussion started by: konvalo
2 Replies
5. Programming
I use Solaris 10, I use following code:
#include <signal.h>
int main(void){
printf("----------testing-----------");
if(signal(SIGUSR1,sig_usr)==SIG_ERR)
err_sys("can't catch SIGUSR1");
for(;;)
pause();
sig_user(int signo){
.....
}
when I run above code,it print nothing... (3 Replies)
Discussion started by: konvalo
3 Replies
6. Programming
hey all, im a new programmer.
i was wondering how you would go about writing the printf function yourself? it is my understanding that when you call printf you are calling an already written function and just providing an argument? if this is the case, is it possible to write that function... (8 Replies)
Discussion started by: Christian.B
8 Replies
7. HP-UX
Hello all!
I have problem in hp-ux 11.11 in awk
I want to grep sar -d 2 1 only 3 column, but have error in awk in hp-ux 11.11
Example:
#echo 123 234 | awk '{print $2}'
123 234
The situattions in commands bdf | awk {print $5}' some...
In hp-ux 11.31 - OK!
How resolve problem (15 Replies)
Discussion started by: ostapv
15 Replies
8. UNIX for Dummies Questions & Answers
#include<stdio.h>
int counter;
int fibonacci(int n)
{
counter += 1;
if ( n <= 2 )
return 1;
else
return fibonacci(n-1) + fibonacci(n-2);
}
int main(void)
{
int i;
int sum ;
for( i = 1 ; i<= 10; i++)
{
counter = 0;
sum... (1 Reply)
Discussion started by: vincent__tse
1 Replies
9. Shell Programming and Scripting
Hello:
I can't get equivalence classes to work in globs or when passing them to tr. If I understood correctly, matches e, é, è, ê, etc. But when using them with utilities like tr they don't work. Here's an example found in the POSIX standard:
I decided to create the aforementioned files in... (9 Replies)
Discussion started by: Cacializ
9 Replies
LEARN ABOUT FREEBSD
_exit
EXIT(2) BSD System Calls Manual EXIT(2)
NAME
_exit -- terminate the calling process
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
void
_exit(int status);
DESCRIPTION
The _exit() system call terminates a process with the following consequences:
o All of the descriptors open in the calling process are closed. This may entail delays, for example, waiting for output to drain; a
process in this state may not be killed, as it is already dying.
o If the parent process of the calling process has an outstanding wait(2) call or catches the SIGCHLD signal, it is notified of the calling
process's termination and the status is set as defined by wait(2).
o The parent process-ID of all of the calling process's existing child processes are set to 1; the initialization process inherits each of
these processes (see init(8) and the DEFINITIONS section of intro(2)).
o If the termination of the process causes any process group to become orphaned (usually because the parents of all members of the group
have now exited; see ``orphaned process group'' in intro(2)), and if any member of the orphaned group is stopped, the SIGHUP signal and
the SIGCONT signal are sent to all members of the newly-orphaned process group.
o If the process is a controlling process (see intro(2)), the SIGHUP signal is sent to the foreground process group of the controlling ter-
minal, and all current access to the controlling terminal is revoked.
Most C programs call the library routine exit(3), which flushes buffers, closes streams, unlinks temporary files, etc., before calling
_exit().
RETURN VALUES
The _exit() system call can never return.
SEE ALSO
fork(2), sigaction(2), wait(2), exit(3), init(8)
STANDARDS
The _exit() system call is expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1'').
HISTORY
The _exit() function appeared in Version 7 AT&T UNIX.
BSD
June 4, 1993 BSD