No, the user does not have write permissions to /opt/core, but only read and execute.
However, we are expecting the core dump to appear in the working directory of the process which is crashing. The user does have write permission to this directory.
I decided to collect some permission data:
The output of errpt -a is as follows, which does not display any Core Dump related failures.
Since the failing process is in a directory with the path /apps/ptadm2/tower/vidm/home/runtime/is/, I assume this is where the core dump would be. The output of the lscore -d is what confuses me. I am unsure which directory the file should appear in -- however due to output of errpt -a, I am unsure whether the system is attempting to generate the core file at all.
I have a requirement to be able to issue selected commands with root privileges but don't have the ability to su to root due to audit requirements dictating that only our UNIX SA's have that feature.
I was told that Powerbroker would allow me to run the commands as root but our security people... (1 Reply)
Whenever i send a mail like: mail <mail id>, a core file is created under /var/spool/mqueue/ path. This is increasing the space of the file system. Why is that core file get created. Does it happens normally. I am getting an errpt error as:
LABEL: CORE_DUMP
IDENTIFIER: B6048838
... (0 Replies)
Hi All,
How to we get to know when say a new log file is created on an Unix box.
I need to trigger a process(say a script) when the new log file is created.
But i need to know by some means or generate a trigger when a new file is created????
Something like when we receive a new mail we... (1 Reply)
Hello,
I have a file Test.txt with 9 columns that looks like this:
1g12 A 14 19 2OAY A 326 331 AAAASA
1l7v A 68 73 1l7v A 68 73 AALAIS
1l7v A 68 73 1XVW B 72 77 AALAIS
1l7v A 68 73 1XXU A 65 70 AALAIS
1l7v A 68 73 1XXU B 65 70 AALAIS
1l7v A 68 73 1XXU C 65 70 AALAIS
1l7v A 68 73 1XXU D... (4 Replies)
Hi,
I have a SCO Unix ver 5.0.7 from which I need to get some files. The problem is that I'm working remotely (have no physical access) and using Dejawin because this server is only has a serial connection to a Windows machine. Ucopy isn't on the server. What I was thinking is to do a print... (5 Replies)
1. The problem statement, all variables and given/known data:
When looking for corefiles, include any file with core in its name. (Some UNIX/Linux systems add the PID of the process that created the core to reduce the chances of overwriting an already existing core file that might be needed. The... (6 Replies)
Hi,
I have used expdp for datapump. The .dmp file is created by the "oracle" user.
my requirement is to make a zipped file of this .dmp file.
What i am trying to do is change the permissions of this .dmp file from 0640 to 0644 and then do a gzip and zip it. Is there any way i can change... (3 Replies)
hi,
i have a script wrriten where there is a temporary files getting created:
echo "From:" ${usrname}@apps.mc.xerox.com>mail_txt
it was working from a long time but now there is a error creating while creating this temporary file. here is the error log for this:... (15 Replies)
Hi,
Currently, we have a Perl script from a third-party vendor that is generating core dumps. It has been reported. We can't turn off the script as it does generate some diagnostic file that's required. So at the moment, we have to let it continue to do its run.
I wish I can say the vendor is... (8 Replies)
Discussion started by: newbie_01
8 Replies
LEARN ABOUT HPUX
coreadm
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)