On Tue, Jan 20, 2009 at 02:55:05PM -0000, Dustin Kirkland wrote:
> On Tue, Jan 20, 2009 at 5:23 AM, Alexander Sack <email address hidden> wrote:
> > would it make more sense to not only probe for the pid, but also whether
> > NM is properly up and responding? One way to do that would probably be
> > nm-tool ... or if thats too much we could send a dbus-send and see if
> > get a reply.
>
> Most init scripts simply check if there's a matching daemon process to
> the specified pid.
>
> However, if there's something more you can do with NetworkManager to
> assert that it's actually running, that's great.
>
> Is this something that you can handle in a subsequent upload, or would
> you rather wait until you have all of this functionality ready?
>
I would like to go for the final solution directly as this should be
committed upstream ... I will talk to debian maintainer to align what
we want.
On Tue, Jan 20, 2009 at 02:55:05PM -0000, Dustin Kirkland wrote:
> On Tue, Jan 20, 2009 at 5:23 AM, Alexander Sack <email address hidden> wrote:
> > would it make more sense to not only probe for the pid, but also whether
> > NM is properly up and responding? One way to do that would probably be
> > nm-tool ... or if thats too much we could send a dbus-send and see if
> > get a reply.
>
> Most init scripts simply check if there's a matching daemon process to
> the specified pid.
>
> However, if there's something more you can do with NetworkManager to
> assert that it's actually running, that's great.
>
> Is this something that you can handle in a subsequent upload, or would
> you rather wait until you have all of this functionality ready?
>
I would like to go for the final solution directly as this should be
committed upstream ... I will talk to debian maintainer to align what
we want.
- Alexander