Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

p_candebug(9) [linux man page]

P_CANDEBUG(9)						   BSD Kernel Developer's Manual					     P_CANDEBUG(9)

NAME
p_candebug -- determine debuggability of a process SYNOPSIS
#include <sys/param.h> #include <sys/proc.h> int p_candebug(struct thread *td, struct proc *p); DESCRIPTION
This function can be used to determine if a given process p is debuggable by the thread td. SYSCTL VARIABLES
The following sysctl(8) variables directly influence the behaviour of p_candebug(): kern.securelevel Debugging of the init process is not allowed if this variable is 1 or greater. security.bsd.unprivileged_proc_debug Must be set to a non-zero value to allow unprivileged processes access to the kernel's debug facilities. RETURN VALUES
The p_candebug() function returns 0 if the process denoted by p is debuggable by thread td, or a non-zero error return value otherwise. ERRORS
[EACCESS] The MAC subsystem denied debuggability. [EAGAIN] Process p is in the process of being exec()'ed. [EPERM] Thread td lacks super-user credentials and process p is executing a set-user-ID or set-group-ID executable. [EPERM] Thread td lacks super-user credentials and process p's group set is not a subset of td's effective group set. [EPERM] Thread td lacks super-user credentials and process p's user IDs do not match thread td's effective user ID. [EPERM] Process p denotes the initial process initproc() and the sysctl(8) variable kern.securelevel is greater than zero. [ESRCH] Process p is not visible to thread td as determined by cr_seeotheruids(9) or cr_seeothergids(9). [ESRCH] Thread td has been jailed and process p does not belong to the same jail as td. [ESRCH] The MAC subsystem denied debuggability. SEE ALSO
jail(2), sysctl(8), cr_seeothergids(9), cr_seeotheruids(9), mac(9), p_cansee(9), prison_check(9) BSD
November 19, 2006 BSD

Check Out this Related Man Page

KILL(2) 							System Calls Manual							   KILL(2)

NAME
kill - send signal to a process SYNOPSIS
#include <sys/types.h> #include <signal.h> int kill(pid_t pid, int sig) DESCRIPTION
Kill sends the signal sig to a process, specified by the process number pid. Sig may be one of the signals specified in sigaction(2), or it may be 0, in which case error checking is performed but no signal is actually sent. This can be used to check the validity of pid. The sending and receiving processes must have the same effective user ID, otherwise this call is restricted to the super-user. If the process number is 0, the signal is sent to all processes in the sender's process group. If the process number is -1 and the user is the super-user, the signal is broadcast universally except to init and the process sending the signal. If the process number is -1 and the user is not the super-user, the signal is broadcast universally to all processes with the same uid as the user except the process sending the signal. No error is returned if any process could be signaled. If the process number is negative but not -1, the signal is sent to all processes whose process group ID is equal to the absolute value of the process number. Processes may send signals to themselves. RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
Kill will fail and no signal will be sent if any of the following occur: [EINVAL] Sig is not a valid signal number. [ESRCH] No process can be found corresponding to that specified by pid. [ESRCH] The process id was given as 0 but the sending process does not have a process group. [EPERM] The sending process is not the super-user and its effective user id does not match the effective user-id of the receiving process. When signaling a process group, this error was returned if any members of the group could not be signaled. SEE ALSO
getpid(2), getpgrp(2), sigaction(2), raise(3). 4th Berkeley Distribution May 14, 1986 KILL(2)
Man Page