11-15-2016
nobody has a magic crystall ball, but it seems that your user just pressed the close button of the window. because the terminal was lost, the system sent SIGHUP (hangup) signal to all applications, which were running in the session. your application can understand this signal and should be able to exit clean. Your stack shows, that it called standard C function exit(). After this call the process should die.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I have problem like everyday i have to check which process consuming more cpu time. I have done it manually using top command..
Is there any script which will tell the exact process name which will consuming more time. I am using hpux. (1 Reply)
Discussion started by: rajesh08
1 Replies
2. Solaris
Hello
Solaris 8 when CPU idle 0 . why nohub process lose ?
Thank (1 Reply)
Discussion started by: ppmanja
1 Replies
3. Ubuntu
I am running a Dell PE R815 with 4 x AMD 12 core CPUs with 128GB of RAM and a RAID 5 array of 6 SAS disks. This is an HPC application and is definitely CPU bound, however once I run 16 of these processes (thus pinning 16 cores) the work performed slows down dramatically, to maybe 5 or 10% of what... (2 Replies)
Discussion started by: mowmentous
2 Replies
4. AIX
ibm tivoli monitor's kuxagent is taking up a lot of cpu usage.
anybody has any idea? i attatched a screenshot. (3 Replies)
Discussion started by: curtis911
3 Replies
5. Linux
Hi All,
Yesterday my Linux server went panic and even a small command took a lot of time to run.
When i monitored pl find the below output
Cpu(s): 0.1%us, 98.4%sy, 0.0%ni, 1.5%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
the time spent on kernel mode is 98 % and also idle time is around 1.5 %...... (4 Replies)
Discussion started by: jegaraman
4 Replies
6. AIX
Hi,
I can't seem to make sense of this. My wait time is showing really high but vmstat's and topas are showing normal usage.
ps aux
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 9961810 5680.7 0.0 448 384 - A Dec 16 6703072:12 wait
... (2 Replies)
Discussion started by: techy1
2 Replies
7. AIX
Dear All,
One production Server is affected by high usage.
Application is slow now. Please guide me how to solve it?
NMON Report shows full cpu usage.
Here im posting some server details.
bash-3.2# lparstat -i
Node Name : *********
Partition Name ... (6 Replies)
Discussion started by: Thala
6 Replies
8. Shell Programming and Scripting
I have created one script and i have added it into cron to run after 10 mins. However I have noted that whenever that script runs, It causes CPU utilization of server to increase about 10-20 %
I have rechecked script and there is no way i can make changes, Script contain only 2-3 commands. So... (4 Replies)
Discussion started by: Nakul_sh
4 Replies
9. Solaris
HI
In my M5000 , one of domain is having SAp installed. from today onwards we are facing some stange issue.
when we start SAP application, that particular user is taking 95 % of system CP and renaming 5 % is taken by system . because of this reason application is slow.
i have 4 CPU(32... (4 Replies)
Discussion started by: bentech4u
4 Replies
10. UNIX for Advanced & Expert Users
Hi Fellas,
Not sure how I can dig in even further but we notice that one of our DB servers is showing high Sys% CPU usage even though when I execute the following command :
I can see that postgres is the only one using the CPU. So if anyone can advise me what would be the best way to... (3 Replies)
Discussion started by: arizah
3 Replies
LEARN ABOUT SUNOS
sigstack
sigstack(3C) Standard C Library Functions sigstack(3C)
NAME
sigstack - set and/or get alternate signal stack context
SYNOPSIS
#include <signal.h>
int sigstack(struct sigstack *ss, struct sigstack *oss);
DESCRIPTION
The sigstack() function allows the calling process to indicate to the system an area of its address space to be used for processing signals
received by the process.
If the ss argument is not a null pointer, it must point to a sigstack structure. The length of the application-supplied stack must be at
least SIGSTKSZ bytes. If the alternate signal stack overflows, the resulting behavior is undefined. (See USAGE below.)
o The value of the ss_onstack member indicates whether the process wants the system to use an alternate signal stack when delivering
signals.
o The value of the ss_sp member indicates the desired location of the alternate signal stack area in the process' address space.
o If the ss argument is a null pointer, the current alternate signal stack context is not changed.
If the oss argument is not a null pointer, it points to a sigstack structure in which the current alternate signal stack context is placed.
The value stored in the ss_onstack member of oss will be non-zero if the process is currently executing on the alternate signal stack. If
the oss argument is a null pointer, the current alternate signal stack context is not returned.
When a signal's action indicates its handler should execute on the alternate signal stack (specified by calling sigaction(2)), sigstack()
checks to see if the process is currently executing on that stack. If the process is not currently executing on the alternate signal
stack, the system arranges a switch to the alternate signal stack for the duration of the signal handler's execution.
After a successful call to one of the exec functions, there are no alternate signal stacks in the new process image.
RETURN VALUES
Upon successful completion, sigstack() returns 0. Otherwise, it returns -1 and sets errno to indicate the error.
ERRORS
The sigstack() function will fail if:
EPERM An attempt was made to modify an active stack.
USAGE
A portable application, when being written or rewritten, should use sigaltstack(2) instead of sigstack().
The direction of stack growth is not indicated in the historical definition of struct sigstack. The only way to portably establish a stack
pointer is for the application to determine stack growth direction, or to allocate a block of storage and set the stack pointer to the mid-
dle. sigstack() may assume that the size of the signal stack is SIGSTKSZ as found in <signal.h>. An application that would like to specify
a signal stack size other than SIGSTKSZ should use sigaltstack(2).
Applications should not use longjmp(3C) to leave a signal handler that is running on a stack established with sigstack(). Doing so may dis-
able future use of the signal stack. For abnormal exit from a signal handler, siglongjmp(3C), setcontext(2), or swapcontext(3C) may be
used. These functions fully support switching from one stack to another.
The sigstack() function requires the application to have knowledge of the underlying system's stack architecture. For this reason, sigalt-
stack(2) is recommended over this function.
SEE ALSO
fork(2), _longjmp(3C), longjmp(3C), setjmp(3C), sigaltstack(2), siglongjmp(3C), sigsetjmp(3C)
SunOS 5.10 28 Feb 1996 sigstack(3C)