Community Packages

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!
Tasklist

FS#32199 - [postgrey] /var/run/postgrey/ is missing

Attached to Project: Community Packages
Opened by Radek Podgorny (rpodgorny) - Wednesday, 24 October 2012, 15:11 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 26 October 2012, 12:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

the postgrey systemd unit contains (among others) "PIDFile=/var/run/postgrey/postgrey.pid"

unfortunately, the daemon fails to start because there's no /var/run/postgrey directory to create the file in.

'mkdir /var/run/postgrey' fixes the problem but this should be part of the package itself.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Friday, 26 October 2012, 12:50 GMT
Reason for closing:  Fixed
Comment by Sergej Pupykin (sergej) - Thursday, 25 October 2012, 10:48 GMT
$ cat /usr/lib/tmpfiles.d/postgrey.conf
d /var/run/postgrey 0755 postgrey postgrey -

so this folder should be created on boot.
Comment by Radek Podgorny (rpodgorny) - Thursday, 25 October 2012, 15:41 GMT
...not on the actual machine to verify that but still... a reboot needed to get it running? really? ;-)

btw, it this an official arch policy to take care of /var/run using tmpfiles? i'd understand this for /run which is mounted as volatile but imho not for /var/run.
Comment by Sergej Pupykin (sergej) - Thursday, 25 October 2012, 17:31 GMT
yes, you need to reboot and /var/run is a symlinks to /run now.
Comment by Radek Podgorny (rpodgorny) - Thursday, 25 October 2012, 17:54 GMT
ok, fair enough... ...still i don't think this is optimal.

anyway, there should be at least a warning during installation. either mentioning a necessity to reboot or a way to trigger tmpfiles action manually (don't know much about this one - is it even possible?). ...or maybe force the trigger automatically during install?


Comment by Sergej Pupykin (sergej) - Friday, 26 October 2012, 12:50 GMT
I added mkdir and chown into post_install() into svn. Should be fixed in next update.

Loading...