On new kernels, /var/run/ is now tmpfs.
This means that its cleaned at every (re)boot.

Some packages (such as puppet or heartbeat) are using subdirectories for PID files (/var/run/puppet/puppet.pid or /var/run/heartbeat/heartbeat.pid).
As you can imagine, after rebooting, these processes are unable to start and require (mkdir /var/run/puppet).

Why haven't packages been updated to fit with this new standard?
Can tmpfs /var/run/ be disabled? How are you handling this situation?

As a temporary workaround, isn't it possible to mount a RAM disk with a predefined tree onto /var/run early after boot? (FYI, I'll run into that issue someday with wpa_supplicant IMHO as it also requires /var/run/wpa_supplicant/.)_________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

OpenRC 0.10 should be able to support tmpfiles.d, which will allow you to create the directory on boot._________________“And even in authoritarian countries, information networks are helping people discover new facts and making governments more accountable.”– Hillary Clinton, Jan. 21, 2010