Yeah I guess I have /var/run/engineyard created from other places.  I also am not using the provided resque recipe because we use resque pool instead which has proven much more reliable.  I agree that consistency between recipes is very important and thus you should follow existing conventions.  Only as a secondary issue I have to note that I don't like this nested directory structure because orphaned pids is something happens quite often on our environments due to long environment loads and the non-bulletproofness of some of these shell scripts, so it's extremely pragmatic to see everything with a `ls -l /var/run/engineyard` instead of having to dig through a couple extra levels of directories for what always ends up being a single file.  Just my $0.02.