9 More Discussions You Might Find Interesting
1. AIX
AIX Version 6.1 and 7.1.
I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device.
It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
2. Red Hat
/ has become full.... So i'm unable to login to the server. What should i do now ??
please help me... Thanks in advance (4 Replies)
Discussion started by: vamshigvk475
4 Replies
3. Linux
Hi can someone tell me what does kill -3 processid does?
kill -3 PID
Would it create a heapdump?
If not , can you tell me how I can create a heapdump of a process in linux?
Or heapdump related to java processes only ? (5 Replies)
Discussion started by: mnassiri
5 Replies
4. Shell Programming and Scripting
/Path/snowbird9/nrfCompMgrRave1230100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.
/Path/snowbird6/nrfCompMgrRave1220100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.
/Path/snowbird14/nrfCompMgrRave920100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.... (0 Replies)
Discussion started by: Shirisha
0 Replies
5. Solaris
Hello Friends,
Need your help !!
I have WebSphere Application Server 6 running on Solaris 10, some of my applications are facing out of memory errors. I have tried increasing the heapsize, still I am getting same messages randomly. I have used kill -3 <PID> to generate the... (1 Reply)
Discussion started by: sahilsardana
1 Replies
6. HP-UX
I'm not a unix admin, just fell into support, so I may be asking a real duh question.
Client runs a PeopleSoft HR/Payrool system. The batch server runs in HPUX PA_RISC 11.11
When a batch process runs, output is written to "staging" directory. When the job finishes, successfully or not, the... (1 Reply)
Discussion started by: abNORMal
1 Replies
7. UNIX for Dummies Questions & Answers
Hi Everyone,
I think I've filled up one of the partitions on my drive. I suspect that one of the applications I've been running has been spitting out junk files to this partition - most of which can be deleted. The problem is that I have no idea how to go look at what's on that partition and... (2 Replies)
Discussion started by: Choppy
2 Replies
8. UNIX for Advanced & Expert Users
Hi Exprts,
I faced this problem several times, which / file system is full (near 100%) and "proc" under that is the main reason.
i don't know how to reduce the size as all directories under proc seems important & other dir/files under / are OS related & could not be removed.
could anyone... (6 Replies)
Discussion started by: nikk
6 Replies
9. UNIX for Advanced & Expert Users
Hi..
i am having a problem, for some reason my / directory is 100 % full.. and i didn't install or anything on it.. it has almost 2 gig on thr root directory.. maybe i am missing some concept because i do not understand why it get full. it is happening on all three of my system.. and i always... (9 Replies)
Discussion started by: souldier
9 Replies
coreadm(1M) coreadm(1M)
NAME
coreadm - core file administration
SYNOPSIS
pattern] pattern] option] option]
[pid...]
[pid...]
[arguments]
[pid...]
DESCRIPTION
The command is used for user space application core file management by specifying the name and the location of core files for abnormally
terminating processes. See core(4).
The command can be used to control system wide and process specific core file placement. The path and pattern is used by the operating
system when generating a core file.
The first form shown in can be used to control system wide core file settings or specify a pattern for init(1M). System administration
privilege is required to change global core file settings. Global core file setting, including the setting for init(1M), is preserved
across system reboot.
Non-privileged users can change per-process core file settings for processes owned by that user. The real or the effective user ID of the
calling process must match the real or the saved user ID of the receiving process unless the effective user ID of the calling process is a
user who as appropriate privileges.
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 over will be truncated to
The possible pattern variables are:
Options
The following options are supported for
Disable or enable the specified core file option. The and options can only be exercised with root privilege.
The valid options for and are:
Allow (or disallow) core dumps using the global core pattern.
Allow (or disallow) core dumps using the per-process core pattern.
Allow (or disallow) core dumps using the global core pattern for
processes.
Allow (or disallow) core dumps using the process core pattern for
processes.
Set the global core file name pattern to pattern.
The pattern must start with an absolute path name which exists and can contain any of the special % variables described in
the section. This option can only be exercised by the super-user.
This is identical to specifying a per-process pattern only that the setting is
applied to init(1M) and is preserved across reboot.
Set the per-process core file name pattern to
pattern for each of the specified process-ID's. The pattern can contain any of the special variables described in and need
not begin with If it does not begin with the core file name will be evaluated relative to the current working directory at
the time of core file creation.
This option can be used by non-privileged users to specify core file settings for processes owned by that user. Super-users
can apply it to any process. The per-process core file will be inherited by the future child processes of the affected pro-
cesses. See fork(2). This option, when invoked without a PID will apply the settings to the calling process (usually the
invoking shell).
This option is used in conjunction with
The option will execute the command specified with the per-process pattern that was specified with
This option can be used to enable or disable core file creation for
the target process. As an example, a user may choose to add the disable in the shell startup script to avoid creation of
core files by that user.
EXAMPLES
The following examples assume that the user has appropriate privilege.
1. To examine the current core file settings:
$ coreadm
global core file pattern:
init(1M) core file pattern:
global core dumps: disabled
per-process core dumps: enabled
global setid core dumps: disabled
per-process setid core dumps: disabled
2. Set global core file settings to include process-ID and machine name and place the core file in the location
$ coreadm -e global -g /mnt/cores/core.%p.%n
A process with PID 1777 on the machine breaker will generate a core file in as (in addition to the core file generated in the CWD of
PID 1777).
3. Examine the per process core file settings for process-IDs 1777 and 1778
$ coreadm 1777 1778
1777: core.%p.%u
1778: /nethome/gandalf/core/core.%f.%p.%t
4. A user can disable creation of core files completely by specifying in the shell startup file (for example,
$ coreadm -P disable $$
$ coreadm $$
1157: (Disabled)
WARNINGS
The output format of may change without notice. Applications parsing the output, should not rely on the compatibility of the output format
between releases.
SEE ALSO
umask(1), init(1M), coreadm(2), core(4).
coreadm(1M)