acocunt lock

acocunt lock

Post by syste » Wed, 09 Aug 2000 04:00:00



When I add a new account , throught dxaccounts.
The error message "The password or group file is currently locked by
another user. Please wait......."
How do I resolve this.

--
Paul Wong Peng Kai
System Engineer
StarHub Internet
Tel: 8257-820

 
 
 

acocunt lock

Post by Jay Vlac » Thu, 10 Aug 2000 04:00:00


Hi,

More than likely an account management command (ex: dxaccounts) terminated abnormally at some point and the lock file is still out there. Do the following:

# ps aux | grep -i dxaccounts

Check to make sure someone else isn't running dxaccounts, or there isn't a runaway process out there. If not, then do the following:

# cd /etc
# ls -al .AM_is_running
# rm .AM_is_running
# dxaccounts

That should work.

 --> Jay


Quote:> When I add a new account , throught dxaccounts.
> The error message "The password or group file is currently locked by
> another user. Please wait......."
> How do I resolve this.

> --
> Paul Wong Peng Kai
> System Engineer
> StarHub Internet
> Tel: 8257-820

--
Spam note: remove all X's from my email address to reply.

Posted with Ink Spot for WinCE
http://www.dejavusoftware.com/

 
 
 

1. Sharing an acocunt - how to reduce risks?

I have stuck an Ultra 60 on eBay to sell

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=8777620487

and for better or worst I have set up an account and let people log in
to test the machine. The username/password are on the eBay listing and
there is only one account, so it is a free for all really.

I realise this is a bit risky, but are wondering what I can do to
minimise risks.

So far, before putting it up, I

1) Patched it with the patches I downloaded a few hours ago

2) Configured my hardware firewall to only allow ftp and telnet to the
box. It also blocks access to the LAN, even if someone gets root on this
machine.

3) Configured ipfilter on the box to block all outgoing connections
except DNS lookup to two DNS servers. So nobody can send mail from it or
use it as a base to hack somewhere else.

4) Changed the ownership of .profile to root and chomod 644, so nobody
can edit it and mess up the path for someone else.

Any other suggestions?

I am aware of other things, like disabling unneeded services, but I
don't want to spend all day on this - that starts taking up a lot of time.

I am mainly concerned with any obvious problems that someone can cause.
Changing .profile seemed on obvious one, so I have thoguht of that. But
have I missed any?

If the machine gets hacked it is not the end of the world. There is no
data of value on it and it can't be used as a base to hack  my LAN due
to the firewall. But I don't really want the hassle of rebuilding it,
should it get hacked.

I'm sure you are going to say I am stupid doing this but I know
sometimes buyers worry about problems on machines they buy, so I thought
by letting them test it, that would reduce that.

--
Dave K

Minefield Consultant and Solitaire Expert (MCSE).

Please note my email address changes periodically to avoid spam.

for a couple of months only. Later set it manually.

2. viewing user/password directory

3. netscape rpm from compaq + my box = lock lock lock

4. PCI Modems & Linux

5. Modem TX and RX status via Num Lock-Caps Lock-Scroll Lock

6. Solaris X86 2.4, when?

7. unable to lock mailbox: no locks available

8. Remote Mksysb

9. More mail file locking questions (lockf, NFS, /var/spool/mail/*.lock)

10. Locking mechanisms / fcntl.c locks.c

11. XScreenSaver lock -> lock console

12. Locked files - who has it locked?

13. Problem with getty leaving locks in /etc/locks