DBUS Issues on ARM

[Shilpa Sheoran]

To give you more info.... My filesystem is READONLY except /usr/local
which has all the dbus files.... Is this a potential prb?
- Hide quoted text -

> cdma-linux # ./dbus-daemon --system --print-address
> 129: Allocated slot 0 on allocator 0x5d0b8 total 1 slots allocated 1 used
> 129: listening on unix socket
> /usr/local/var/run/dbus/system_bus_socket abstract=0
> 129: Read 12 bytes from /dev/urandom
> 129: Initialized server on address
> unix:path=/usr/local/var/run/dbus/system_bus_socket,guid=d215c5d1ba61a9e60bfd910012d54a02
> 129: Adding a read watch on fd 3 using newly-set add watch function
> unix:path=/usr/local/var/run/dbus/system_bus_socket,guid=d215c5d1ba61a9e60bfd910012d54a02
> 129: Allocated slot 0 on allocator 0x5d05c total 1 slots allocated 1 used
> 129: Becoming a daemon...
> 129: chdir to /
> 129: forking...
> 129: parent writing pid file
> 130: in child, closing std file descriptors
> 129: parent exiting

On 3/16/07, Thiago Macieira <thiago at kde.org> wrote:
> Shilpa Sheoran wrote:
> >The Server verbose mode output is as follows - using
> > ./arm-linux-dbus-launch
>
> Don't use dbus-launch. Run dbus-daemon manually.
>
> --
>  Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>   PGP/GPG: 0x6EF45358; fingerprint:
>   E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
>
>