coreadm(2)							System Calls Manual							coreadm(2)

NAME

       coreadm - application core file administration

SYNOPSIS


DESCRIPTION

       system  call  is  used to specify the location and pattern for core files produced by abnormally terminating processes.	See core(4).  This
       system call can be used to specify a system wide location for core file placement and/or a process specific pattern.

       The structure, is used to specify a system wide or a per-process core file pattern and also specify the current system wide core file  set-
       tings.  is defined in the header

       Member Type   Member Name   Description

       char	     c_pattern	   The core file pattern.
       uint64_t      c_flags	   Core file settings.

   Parameters
       is expected to be set to It is critical for future backward compatibility that the macro itself be used and not its value.

       is  the	core  file  pattern.  A core file name pattern is a normal file system path name with embedded variables, specified with a leading
       character, that are expanded from values in effect when a core file is generated by the	operating  system.   An  expanded  pattern  length
       greater than will be truncated to

       The possible values are:

       c_flags is used to control the system wide core file settings.  The flag values can be combination of

       Enable/Disable creation of global core files.

       Enable/Disable creation of per-process core files.

       Enable/Disable creation of global core files for
	      processes.

       Enable/Disable creation of per-process core file for
	      processes.

       If a flag value is not set, then the option is disabled.

       For  per-process  core  file  setting,  c_flags can either be 0 or The former disables core file creation (for that process) and the latter
       enables it.

       c_pid	 Should be a (valid) pid of a target process or 0.  If c_pid is zero, then the settings are applied to global core file  settings.
		 If c_pid is 1, then the settings are applied to init(1M).

       c_in	 If non-NULL, then the values will be used as new core file settings.  If this is NULL, then the c_out parameter is expected to be
		 non-NULL and system call is used to interrogate the current settings.

       c_out	 If non-NULL, the current settings are returned in this parameter.

RETURN VALUE

       Upon successful completion, returns 0. Otherwise, a value of -1 is returned and is set to indicate the error.

ERRORS

       fails and does not change the core file settings if
		    the effective user-ID of the calling process is not a user having appropriate privileges.

       The input or output parameter passed to
		    is an invalid address.

       The core file pattern or flags is invalid.

       The specified PID is non-zero and does not exist.

EXAMPLES

       1. Enable global core file creation using the pattern (core.process-ID.machine-name) in the location

       2. Enable per-process core file pattern for the process-ID passed in as argument.   The	core  file  will  be  placed  in  The  pattern	is
	  (core.process-ID.time-stamp).

       3. Enable  a   per-process  pattern  of core.CUP-ID for all processes in the system (init(1M) core file setting).  NOTE: This has to be run
	  during system startup or reboot the machine after setting this for the settings to take full effect.

SEE ALSO

       coreadm(1M), exec(2), fork(2), pstat(2), ttrace(2), core(4).

STANDARDS CONFORMANCE

																	coreadm(2)