On 10/02/2013 17:29, [email protected] wrote: > I had to actually prevent the migration to /run by changing the > boot.misc script because if I do not do that, a number of subdirectories > which I had created in /var/run were not in /run and a number of apps > would not start properly and indeed it is not taking much space, so I am > not sure why anyone bothered. The only other option would have been to > write something to fix the /run, but that was not what I wanted to do. > /var/lock had this same problem also.
Why would you do that? /var/run is broken as the destination folder for what is intended to go in it, and it has been broken since day 1: /var/run is only available once /var is available or mounted. The contents of /var/run are often needed before /var is mounted. /run is the correct place for this. Problems with the migration are solved using the mv command -- Alan McKinnon [email protected]
