| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 9804.1 | | NNTPD::"[email protected]" | Ann Majeske | Tue May 13 1997 18:52 | 6 |
| I'm not sure what locking method dxaccounts uses, but you could try
looking for passwd:t, passwd:o, group:t, and/or group:o. Of course,
the obvious is to look for anything *passwd* and/or *group*. Just make sure
that you keep a copy of anything you delete (under another name), just in
case it wasn't the lock file ;^)
[Posted by WWW Notes gateway]
|
| 9804.2 | | CSC64::BLAYLOCK | If at first you doubt,doubt again. | Wed May 14 1997 13:59 | 30 |
|
Try looking for the file: /etc/.AM_is_running
This file is created by the new /usr/shlib/libaccmgr.so file from
the Patch ID: OSF405DX-400005 (this is the 4.0a variant).
From the readme:
"PROBLEM: (QAR 39332) (Patch ID: OSF405DX-400005)
********
Running two conncurrent instances of the account management commands is not
supported. This restriction applies to the dxaccounts graphical user interface
and the useradd, usermod, userdel, groupadd, groupmod, and groupdel commands.
This restriction was release noted for Digital UNIX V4.0 and it is now enforce
in the software.
In order to prevent concurrent access, each account management command creates
a lock file at startup called /etc/.AM_is_running. If any of the commands are
terminated abnormally (e.g. kill -9) then this lock file will not be deleted
and future command invocations will refuse to run with the error message:
The password and group files are currently locked by another user.
Please try again later.
This message means that the account database files are either legitimately
locked OR one of the commands terminated abnormally leaving an
/etc/.AM_is_running lock file. If no other root users are using the account
management commands, simply delete the lock file. "
|
| 9804.3 | | GERUND::WOLFE | I'm going to huff, and puff, and blow your house down | Wed May 14 1997 15:05 | 29 |
| What version of the OS are you running and have you installed
any patch kits?
The V4.0 version of dxaccounts creates that standard lock files:
/etc/ptmp is the lock file for /etc/passwd
/var/yp/src/passwd.ptmp is the lock file NIS
These are the standard lock files used by vipwd and the rest
of the passwd file related commands.
In a patch kit, we additionally introduced dxaccounts specific
lock file that serializes access to the passwd and group files
for the dxaccounts gui and the cli commands (useradd, userdel, etc).
That lock file is /etc/.AM_is_running and is described in the
patch kit release notes.
If you find a case where dxaccounts is crashing and leaving lock
files *please* qar it. It might already be fixed in a patch kit
as well so you can check there and see if the list of fixed
bugs looks like it applies to you.
When entering a bug report please provide the following info:
- what operation you performed that led to the crash
- are you running NIS
- are you running C2.
Thanks.
pete
|
| 9804.4 | Ok, /etc/.AM_is_not_running now. | TRN02::FRASSINO | | Fri May 16 1997 04:55 | 5 |
| Hi,
thanks to all for the suggestions !!
I deleted /etc/.AM_is_running and all is running again !!!!!!!
*8-) Pierpa
|