10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I want to delete all files and folders owned a user say abcuser in the folder /tmp .
Can you please give me the command ?
Thanks
Matt (2 Replies)
Discussion started by: lijjumathew
2 Replies
2. Web Development
Hi
I am trying to make a web program which is command line equivalent. i have done the coding in cgi program in perl and html for basic forms to take inputs. when i ran the program from web application i see permission denied messages. after analyzing i found apache is running as wwwrun which... (2 Replies)
Discussion started by: rakeshkumar
2 Replies
3. AIX
Hi
I'm logged in to an AIX box now and we need to do an audit on this box.
cbssapr01:# pwd
/
Which command will show all the files and directories owned by root user with permissions as 777 ? (8 Replies)
Discussion started by: newtoaixos
8 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I want to know if the is a way I can list the directories owned by a given user. Say i am logged in as that user.
I found out the find command lists the files owned by a certain user/group
but i want to know only the directories and if possible the permissions associated with these... (6 Replies)
Discussion started by: poojabhat
6 Replies
5. UNIX for Dummies Questions & Answers
I've tried to figure this out.
I'm only about 6 mos into my AIX admin duties, but I've got a "security" problem I can't figure out.
I've created a sub directory as follows:
drwx------ 2 root system 256 Apr 13 16:02 mike
I've logged in another session with the following user:
$ id... (2 Replies)
Discussion started by: mpheine
2 Replies
6. Shell Programming and Scripting
Hi All,
I am writing a script in which i need find the total size of all the directories that are present in a directory which are owned by a particular user.
I will explain in details
i have a dir DIR1 in which i have 5 dir's DIRA DIRB DIRC DIRD DIRE.
DIRA DIRC DIRE are owned by "eswar" i... (2 Replies)
Discussion started by: firestar
2 Replies
7. UNIX for Advanced & Expert Users
How can I kill a process owned by user1? I will be using another user (user2) (not root) and we are on the same primary and secondary group. I copied everything including it's .profile and set the path accordingly.
user1@hostnmae0:/home/user1 $ pkill java
pkill: Failed to signal pid 1234:... (2 Replies)
Discussion started by: lhareigh890
2 Replies
8. Shell Programming and Scripting
Hi Here is my problem:
1)I am login to unix server through my login id and do SU - xxx
2) Start the script which is running in background
I want that other user which login to there id and do SU - yyy(Different user) kill that
script.
Could you please help me in this. (9 Replies)
Discussion started by: mr_harish80
9 Replies
9. Cybersecurity
Under oracle user file abc.txt was created. Oracle user belong to dba group on UNIX Server. However other non Oracle users which belongs to some other network groups need read only access to this file.
Every time when I login as other then oracle user and try to view this file it saying that I... (2 Replies)
Discussion started by: groosha
2 Replies
10. UNIX for Dummies Questions & Answers
Hi I am an Oracle DBA and I want to delete everything owned byOracle on the AIX server.
What command would do that? (5 Replies)
Discussion started by: sarangishere
5 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)