Technical article 100782

The make(CP) command core dumps for certain users under OpenServer 5.0.0.

OpenServer 5.0.0

Written · Last revised

Problem

The make(CP) command always core dumps for certain users. For example:

$12 make
Memory fault(coredump)

Other users are able to use the make(CP) command without difficulty.

Cause

A known problem exists when the user invoking the make(CP) command has a gid (group-id) that is not present in /etc/group.

Solution

Check the user's gid using the id(C) command:

$13 id
uid=201(testuser) gid=100 groups=100,50(group)

If the gid does not have an appended group name in parenthesis, the gid is not present in /etc/group.

To allow the user to use the make(CP) command, either change the "Login Group" to a valid group using the scoadmin selection:

scoadmin -> Account Manager -> Users (Modify) ->
Change Group Membership -> Login Group
as shown below:
|------------                                                     -----------|
||----------- |------- sconan:  Change Groups:  testuser -------| ----------||
||  Host      |                                                 |#     Help ||
||            | Login Group:  |--------|                        |#          ||
|  |--------- |               ||100__|v|                        |#--------|  |
|  |          |               ||=============|                  |#        |# |
|  |          |                ||----------| |                  |#        |# |
|| |          | Member of:     ||*adm      ^ |Other Groups:     |#        |# |
|| |          | |--------------|| asg      * ||--------------|  |#_______||# |
|| | -------- | | group        || audit    | || adm          ^  |#------- |# |
|| |          | |              || auth     | || asg          *  |#        |# |
|| |      Log | |              || backup   | || audit        *  |#. ]     |# |
|| |  Distrib | |              || bin      v || auth         |  |#..)]    |# |
|| |   Home D | |              ||----------| || backup       |  |#y... ]  |# |
|| |      Log | |              |=============|| bin          |  |#hip... ]|# |
|| |          | |              v              | cron         v  |#        |# |
|| |--------- | |<************>|              |<************>|  |#--------|# |
|| |[   OK    |                                                 |#[  Help]|# |
|| |--------- |                               Search for:       |#--------|# |
||  ######### |                               |_______________| |########### |
|             |                                                 |#           |
|------------ |-------------------------------------------------|#-----------|
|             |[   OK   ]          [ Cancel ]         [  Help  ]|#           |
|------------ |-------------------------------------------------|#-----------|

Or add a group with the gid of the user using the scoadmin selection:

scoadmin -> Account Manager -> Groups (Add New Group)

and specifying a name for the user's gid, as shown below:

|----                                                                      --|
||--- |===================== sconan: Add New Group ======================| -||
||  H |                                                                |#lp ||
||--- |       Group Name:  |example__|                                 |#---||
| Use |         Group ID:  |100 __|                                    |#    |
|     |  Distributed Via:  | ______________|   [(Change Distribution.)]|#    |
| Sta | -------------------------------------------------------------- |#    |
||--- |                                                                |#--| |
||*   |          Users In Group                Other Users             |#  ^ |
||    |          |--------------| [(Remove >>)]|--------------|        |#  * |
||    |          |              ^ [( << Add  )]| adm          ^        |#  * |
||    |          |              *              | asg          *        |#  * |
||    |          |              *              | audit        |        |#  * |
||    |          |              *              | auth         |        |#  * |
||    |          |              *              | backup       |        |#  | |
||    |          |              v              | bin          v        |#  | |
||    |          |<************>|              |<************>|        |#  | |
||    |                                                                |#  | |
||    |          Search for:                   Search for:             |#  v |
||<** |          |_______________|             |_______________|       |#->| |
|     |                                                                |#    |
|---- |Use next ID as supplied, or enter group ID number               |#----|
|     |----------------------------------------------------------------|#    |
|---- |[   OK   ]                  [ Cancel ]                [  Help  ]|#----|

See also

passwd(F), group(F), id(C).

TA103851, "How can I tell what program produced a core dump?".

From the Xinuos technical article database, record 100782. Reproduced with permission. The original is at www.sco.com/ta/100782, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.