Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34262 - [postgrey] Use POSTGREY_ADDR in postgrey.service
Attached to Project:
Community Packages
Opened by Jochen Keil (jrk) - Monday, 11 March 2013, 19:45 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 15 April 2013, 11:17 GMT
Opened by Jochen Keil (jrk) - Monday, 11 March 2013, 19:45 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 15 April 2013, 11:17 GMT
|
DetailsDescription:
postgrey.service calls postgrey like this: ExecStart=/usr/sbin/postgrey --inet=127.0.0.1:10030 \ --group=postgrey --user=postgrey $POSTGREY_OPTS --pidfile=/var/run/postgrey/postgrey.pid \ --greylist-text="${POSTGREY_TEXT}" In /etc/conf.d/postgrey (which is already defined as environment file) one can define POSTGREY_ADDR. However, this variable is not used atm, instead the tcp socket is hardcoded. Additional info: community/postgrey 1.34-10 Steps to reproduce: cat /etc/conf.d/postgrey cat /usr/lib/systemd/system/postgrey.service |
This task depends upon
EnvironmentFile=-/etc/conf.d/postgrey
The other variables (POSTGREY_OPTS, POSTGREY_TEXT) are used as well in the .service file.
If you want to remove the conf.d file please provide other means for configuring postgrey.
EnvironmentFile=-/etc/conf.d/postgrey
Moreover I heard that latest systemd allows to override parts of service files using /etc/systemd/. So this is not a bug.