Unnecessary to keep that dir, because it's created in init script of proftpd. Blocks #332633. Reproducible: Always Steps to Reproduce: 1. emerge proftpd Actual Results: keeps dir /var/run/proftpd Expected Results: Shouldn't keep that dir.
Thanks for your report! This issue does only affect the ProFTPD 1.3.3 series (proftpd-1.3.3e.ebuild and proftpd-1.3.3f.ebuild). If any Gentoo Developer reads this bug report: Feel free to remove the line "keepdir /var/run/proftpd" from both ebuilds. Thanks.
I see. So this will be automatically fixed with stabilization of proftpd-1.3.4.
(In reply to comment #2) > I see. So this will be automatically fixed with stabilization of proftpd-1.3.4. Yes. This issue was fixed in proftpd-1.3.4_rc1-r1.ebuild. But generally I do not backport such changes to the ProFTPD 1.3.3 ebuild series which is stable for a long time. In a few days I want to start the stabilization process of proftpd-1.3.3f.ebuild. And as long as there are just ProFTPD 1.3.4 release candidates and upstream releases bugfix and security releases of the ProFTPD 1.3.3 series I am not planing to stabilize any ProFTPD 1.3.4* ebuild. I believe that it will take some month until there will be a stable ProFTPD 1.3.4 release. Hence we should backport this change to ProFTPD 1.3.3* and drop this line in both ebuilds. There is no reason why it has to stay in those ebuilds because all (1.3.3* and 1.3.4*) ebuilds are using the same init script which creates this runtime directory.
Fixed in 1.3.3{e,f} ebuilds, thanks Bernd!
It still uses /var/run all over the place.
*** Bug 510644 has been marked as a duplicate of this bug. ***
Is anyone working on this, or shall I start on ebuild patches tomorrow? This looks to have been forgotten.
Current stable proftpd-1.3.5b does not install anything to /var/run $ equery f proftpd | grep /var /usr/include/proftpd/var.h /var Init system (and tools) assumes /var/run to be present (be it a symlink to /run or a separate directory). But that is fine.
