[courier-users] stucked within a LOCK

[Zsolt Kiss Gere]

Hi,   I have recommended and installed the Courier mail server at a customer. We create new mail users by exec-ing a shell script from an application, which calls in turn userdb. The method seems to work, but we have a problem. Sometimes the script fails with the following error:   “Can’t open /usr/lib/courier/etc/.lock.userdb: Permission denied at /usr/lib/courier/sbin/userdb line 83.”   The .lock.userdb file has permissions 600 for root.daemon at that time. Usually the owner of this file is not root, but user.courier, the account at which the mail server was installed, and our application and the shell scripts run. It is so (and working) when (our) shell scripts create the lock.   But it seems that another (daemon) process creates the lock file at some time, with permissions only for root, and then leaves it there. The user creation, run with user privileges cannot then be fulfilled.   What can we do?   Thanks for any help,     Zsolt