Dapper is mucking with my /var/run/ dirs

[nodata]

> On Wed, 2006-05-31 at 14:59 -0700, Carlos Picazzo wrote:
>> On 5/31/06, Carlos Picazzo <ojaiguy at gmail.com> wrote:
>> > I've got some custom directories in /var/run/ and after upgrading to
>> > dapper, I've noticed that those directories, for some reason, are
>> > being removed automatically.  Now when my box comes back up, it starts
>> > puking because it can't write to its normal file.  What's going on and
>> > how can I fix this so it doesn't continue to happen?
>>
>> Well, after a little more digging, it appears that /var/run in Dapper
>> is a tmpfs and gets recreated at boot time.  Is there a config file
>> where you can specify what dirs should get created and their perms?
>>
>
> I have the same problem. Although I was stupid to set up something
> permanently to /var/run, I'd also love to have old behaviour back. Did
> you have luck with it?
>
> 	Mike

If an ubuntu package relies on /var/run/SOMEDIR, and it's not there, you
need to report this as a bug. But I don't think this is your problem.

If the script you are calling has an /etc/defaults/NAME file, you can
cheat (and this is a horrible, horrible hack), and do a mkdir
/var/run/BLAH in it.

If it doesn't have one of those, then you've probably written the init
script, and can update that instead.