Public bug reported:
I've just started using amavisd-milter on an 'older' (i.e. slow) server,
and I encountered a problem with the init.d startup script (/etc/init.d
/amavisd-milter): The script would successfully use "start-stop-daemon
$START" to launch the /usr/sbin/amavisd-milter process, but would then
attempt to set the ownership (chown) and permissions (chmod) on the unix
socket before the /usr/sbin/amavisd-milter process had created the
socket.
This meant that the ownership and permissions specified in /etc/default
/amavisd-milter would fail to have any effect (or in some cases, setting
the ownership would fail but setting the permissions would succeed).
The solution to this problem is to have the startup script wait until
the socket is created, before attempting to set the ownership and
permissions.
I've updated the script on my server to resolve the problem, and I'd
like to submit this as a patch, but I'm having trouble finding out which
project to check out (i.e. with bzr branch lp:PROJECT-NAME)? Perhaps it
is because there is an upstream project that I should be using instead?
Please point me in the right direction?
System information:
# lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
# apt-cache policy amavisd-milter
amavisd-milter:
Installed: 1.5.0-5
Candidate: 1.5.0-5
Version table:
*** 1.5.0-5 500
500 http://nz.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status
Thanks,
Nick.
** Affects: amavisd-milter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915501
Title:
init.d script fails to set socket ownership and permissions on slower
systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
