{"issue":{"state":"open","created_at":"2011-12-05T00:06:00Z","updated_at":"2011-12-05T00:06:00Z","comments":0,"user":{"gravatar_id":"24ff03200290b25a8d57163e3ef5554e","id":34627,"url":"https://api.github.com/users/betelgeuse","avatar_url":"https://secure.gravatar.com/avatar/24ff03200290b25a8d57163e3ef5554e?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"betelgeuse"},"body":"http://docs.engineyard.com/adding-cron-jobs.html\r\n\r\n```bash\r\n/usr/bin/lockrun --lockfile=/tmp/jobname.lockrun -- sh -c \"cd /data/appname/current && rake RAILS_ENV=production some:task\"\r\n```\r\n\r\nhttp://unixwiz.net/tools/lockrun.html\r\n\r\n```\r\nIMPORTANT: Be sure to place the lockfile in a directory that only that user has the rights to, and not in /tmp (as this Tech Tip has previously suggested). If a different user has the ability to write to the directory, s/he could create a symbolic link from the target lockfile to some system file that uses locks the same way, and get the cron job to foul up the locking. \r\n```\r\n\r\nAs the instances are not multi user this is not a big concern but better to go with best practises.","assignee":null,"id":2444581,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":210,"labels":[],"title":"Should not recommend to put lockrun files to /tmp","html_url":"https://github.com/engineyard/ey-docs/issues/210","closed_at":null,"url":"https://api.github.com/repos/engineyard/ey-docs/issues/210","milestone":null},"action":"opened"}