The reason for the lock failure is now indicated in the failure message.

This commit is contained in:
nekral-guest
2011-07-14 17:20:29 +00:00
parent 8e4062eaad
commit ff21533772
9 changed files with 9 additions and 0 deletions
@@ -1 +1,2 @@
gpasswd: existing lock file /etc/group.lock without a PID
gpasswd: cannot lock /etc/group; try again later.
@@ -1 +1,2 @@
gpasswd: existing lock file /etc/gshadow.lock without a PID
gpasswd: cannot lock /etc/gshadow; try again later.
@@ -1 +1,2 @@
groupadd: existing lock file /etc/group.lock without a PID
groupadd: cannot lock /etc/group; try again later.
@@ -1 +1,2 @@
groupadd: existing lock file /etc/gshadow.lock without a PID
groupadd: cannot lock /etc/gshadow; try again later.
@@ -1 +1,2 @@
groupdel: existing lock file /etc/group.lock without a PID
groupdel: cannot lock /etc/group; try again later.
@@ -1 +1,2 @@
groupdel: existing lock file /etc/gshadow.lock without a PID
groupdel: cannot lock /etc/gshadow; try again later.
@@ -1 +1,2 @@
groupmod: existing lock file /etc/group.lock without a PID
groupmod: cannot lock /etc/group; try again later.
@@ -1 +1,2 @@
groupmod: existing lock file /etc/gshadow.lock without a PID
groupmod: cannot lock /etc/gshadow; try again later.
@@ -1 +1,2 @@
groupmod: existing lock file /etc/passwd.lock without a PID
groupmod: cannot lock /etc/passwd; try again later.