Advertisement

08.28.2008 at 08:16AM PDT, ID: 23685852
[x]
Attachment Details

How to enable per-process core file on Solaris 9 platform?

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.8
I am following the article http://www.sun.com/bigadmin/content/submitted/per_process_path.jsp to enable the per-process core file on my Solaris 9 platform. But it seems not work for me. Here are the details:

----------------------------------------------------------------------------------------------------------------------

SunOS 5.9

login: user2
Password:
Last login: Thu Aug 28 11:04:38 from acartazk.ca.nor
Sun Microsystems Inc.   SunOS 5.9       Generic May 2002
$ coreadm
     global core file pattern: /var/core/core.%f.%p
       init core file pattern: core
            global core dumps: enabled
       per-process core dumps: enabled
      global setid core dumps: enabled
 per-process setid core dumps: enabled
     global core dump logging: enabled
$ who am i
user2      pts/2        Aug 28 11:05    (acartazk.ca.nortel.com)
$ coreadm $$
663:    /export/home/user2/corefiles/core_%n_%f_%u_%g_%t_%p
$ ls -ld /export/home/user2/corefiles
drwxr-xr-x   2 user2    other        512 Aug 27 18:01 /export/home/user2/corefil
es
$ ps -ef | grep user2
   user2   673   663  0 11:06:28 pts/2    0:00 ps -ef
   user2   674   663  0 11:06:28 pts/2    0:00 grep user2
   user2   663   661  0 11:05:22 pts/2    0:00 -ksh
   user2   592   590  0 10:52:51 pts/1    0:00 -ksh
$ gcore 663
gcore: core.663 dumped
$ pwd
/export/home/user2
$ ls -l
total 1250
-rw-r--r--   1 user2    staff     203560 Aug 28 11:06 core.663
drwxr-xr-x   2 user2    other        512 Aug 27 18:01 corefiles
$ coreadm 663
663:    /export/home/user2/corefiles/core_%n_%f_%u_%g_%t_%p
$

----------------------------------------------------------------------------------------------------------------

Also I have a puzzle about the core file permission. The coreadm man page says:

    When generated, a global core file will be created mode  600
    and  will  be  owned by the super-user. Non-privileged users
    cannot examine such files.

    Ordinary per-process core files are created mode  600  under
    the credentials of the process. The owner of the process can
    examine such files.

But the core generated by gcore has permission 644.  
Answered By: Rowley
Expert Since: 12/10/2002
Accepted Solutions: 98
Computer Expertise: Advanced
Rowley has been an Expert for 6 years1 month, during which he has posted 334 comments and answered 98 questions. Rowley is just one of 129 experts in the Unix Setup Zone. 2 experts collaborated on this answer, which was graded an "A" by the asker.
 
 
 
 
20081119-EE-VQP-47 / EE_QW_2_20070628