Sponsored Content
Full Discussion: Svhptdaemon
Operating Systems HP-UX Svhptdaemon Post 302989054 by bbbngowc on Friday 6th of January 2017 02:03:47 PM
Old 01-06-2017
Quote:
Originally Posted by jim mcnamara
How do you attribute the 50% sys usage to that one process? That is for all processes is it not? BTW - when ANY process runs it spends time in kernel code (sys) when invoking a syscall, .e.g. open(). That means vmstat and sar would normally show a summed % sys for all processes system wide.

Doesn't mean that the daemon is or is not using most of that %.
My mistake. I was trying to say the same thing you just did. The usage is around 50%.
 
FORK(2) 							System Calls Manual							   FORK(2)

NAME
fork - spawn new process SYNOPSIS
fork( ) DESCRIPTION
Fork is the only way new processes are created. The new process's core image is a copy of that of the caller of fork. The only distinc- tion is the fact that the value returned in the old (parent) process contains the process ID of the new (child) process, while the value returned in the child is 0. Process ID's range from 1 to 30,000. This process ID is used by wait(2). Files open before the fork are shared, and have a common read-write pointer. In particular, this is the way that standard input and output files are passed and also how pipes are set up. SEE ALSO
wait(2), exec(2) DIAGNOSTICS
Returns -1 and fails to create a process if: there is inadequate swap space, the user is not super-user and has too many processes, or the system's process table is full. Only the super-user can take the last process-table slot. ASSEMBLER
(fork = 2.) sys fork (new process return) (old process return, new process ID in r0) The return locations in the old and new process differ by one word. The C-bit is set in the old process if a new process could not be cre- ated. FORK(2)
All times are GMT -4. The time now is 06:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy