On 12/04/2015 10:59 AM, Patrick O'Callaghan wrote:
On Fri, 2015-12-04 at 09:30 -0800, Rick Stevens wrote:
To make sure the lockfile gets deleted, you must create a function
that deletes the lockfile, and specify that function in a trap call
to trap SIGINT, SIGTERM, etc. That way it cleans up aft
On Fri, 2015-12-04 at 09:30 -0800, Rick Stevens wrote:
> To make sure the lockfile gets deleted, you must create a function
> that deletes the lockfile, and specify that function in a trap call
> to trap SIGINT, SIGTERM, etc. That way it cleans up after itself if
> you abort it.
For Shell scripts
On 12/04/2015 05:29 AM, Frédéric Bron wrote:
in fact, I just had to delete the .lock file. I do not understand why
it was there.
Many commands create a lock file so that you can't run multiple copies
of the command simultaneously. If you had two users running that
command, both writing to the s
in fact, I just had to delete the .lock file. I do not understand why
it was there.
Thanks,
Frédéric
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraprojec
On 12/03/2015 10:37 AM, Frédéric Bron wrote:
On fedora 23 the following command does not work anymore:
$ passwd -u username
Unlocking password for user username.
passwd: Libuser error at line: 171 - Invalid contents of lock
`/etc/shadow.lock'.
passwd: Error (password not set?)
What can I do to
On fedora 23 the following command does not work anymore:
$ passwd -u username
Unlocking password for user username.
passwd: Libuser error at line: 171 - Invalid contents of lock
`/etc/shadow.lock'.
passwd: Error (password not set?)
What can I do to unlock this user?
Frédéric
--
users mailing l
