Summary: | _dbus_spawn_async_with_babysitter with environment pointer (win32) | ||
---|---|---|---|
Product: | dbus | Reporter: | Ralf Habacker <ralf.habacker> |
Component: | core | Assignee: | Havoc Pennington <hp> |
Status: | RESOLVED FIXED | QA Contact: | John (J5) Palmieri <johnp> |
Severity: | normal | ||
Priority: | high | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
added environment argument to _dbus_spawn_async_with_babysitter()
updated patch |
Description
Ralf Habacker
2006-08-21 00:39:52 UTC
Created attachment 6627 [details] [review] added environment argument to _dbus_spawn_async_with_babysitter() Created attachment 6630 [details] [review] updated patch Added missing dbus/dbus-spawn.h what about the higher-level question - does it make sense to use the "babysitter" on Windows? I see in the quoted mail I referred to some previous discussion of that, but I don't remember it. I guess there are two uses: - service activation by the daemon - dbus-launch how do these work on windows and how should they work / what would the "windows native" approach be? - service activation is working on windows too I don't know what dbus-launch has to do with this. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.