Red Hat Bugzilla – Bug 162334
milter-greylist has broken initscript
Last modified: 2007-11-30 17:11:09 EST
The initscript for milter-greylist isbroken. There are fixed parameters for PID
file, socket path and run-as-user. Commandline arguments take precedence of
config file so editing config file is worthless and editing init scripts means
that the next update will remove our changes.
So please apply the attached patch to honor config file and allow to override
command line parameters via /etc/sysconfig/milter-greylist. The patch does not
change current behavior, just add new feature.
Working RPM package with SRC package could be found at:
Created attachment 116299 [details]
Patch for init script for milter-greylist
Created attachment 116300 [details]
This /etc/sysconfig/milter-greylist file is like other config files for
initscriptsin FC or RHEL (httpd, sendmail etc).
You have to add this file to the SPEC file, see URL above with working packages
for RHEL3 and RHEL4.
Created attachment 116534 [details]
Fixed patch for init script
There was a wrong patch to the socket file in the first (now obsoleted) patch.
Created attachment 116536 [details]
Fixed /etc/sysconfig/milter-greylist file
Same wrong path to the socket file has been fixed.
Created attachment 116537 [details]
Patch for SPEC file to utilize /etc/sysconfig/milter-greylist
Just to show how the SPEC file should be changed to utilize
While making such changes please put the socket into /var/run by default.
Above is the FHS reference for the /var/run directory. Below is the relevant
"System programs that maintain transient UNIX-domain sockets must place them
in this directory"
ok, I changed 1.6 (FC-4) to read /etc/sysconfig/milter-greylist so that
'OPTIONS' can be overridden there.
I did not added the GRUSER/GRSOCKET/GRPIDFILE code because it is too complicated
for an initscript and slows down the bootprocess. It won't be compatible with
In FC-5/devel branch, the user and socket will be set in the configfile only.
I changed the location of the socket as suggested in comment #6, too. But only
in devel, not in FC-4 because an upgrade might break existing installations else.