/tmp/hald-local and /tmp/hald-runner
David Zeuthen
david at fubar.dk
Tue May 2 10:52:34 PDT 2006
On Tue, 2006-05-02 at 10:30 -0700, Artem Kachitchkine wrote:
> Joe Marcus Clarke wrote:
> > These two directories are vital for HAL to startup. Yet I do not see
> > them created anywhere. If they are not created manually prior to
> > starting hald, then hald will die. I checked the dbus code, but they do
> > not appear to be created there, either. I'm wondering how this works on
> > Linux. My thoughts on fixing this were to add mkdir(2) calls to
> > hald_dbus.c and hald_runner.c just before dbus_server_listen() is
> > called.
>
> Aren't they abstract sockets in Linux? Abstract sockets don't have
> filesystem representation, so they are not affected by the problem you
> described.
That is correct.
> On Solaris, I create these directories in the hal startup
> script.
Maybe hald should create them when starting up?
> I was also thinking about moving them somewhere safer, such as
> /var/run/hal.
Sounds good with me.
David
More information about the hal
mailing list