Dapper is mucking with my /var/run/ dirs
ojaiguy at gmail.com
Fri Jun 9 05:53:41 UTC 2006
Yes, I did what apparently most people are doing -- adding something into
the init script to create the dir if it doesn't exist. Pretty lame to have
to do (IMHO) -- it's even in the apache2 init script!:
[ ! -d /var/run/apache2 ] && mkdir /var/run/apache2
Anyway, that's what I did and yeah, it seems like a bad idea (again, IMHO)
On 6/1/06, Mario Splivalo <mario.splivalo at mobart.hr> wrote:
> 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?
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ubuntu-users