Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Aug 7, 2015, 2:47:49 AM (8 years ago)
- Author:
-
mmcco
- Comment:
-
startup gconf removed, proxy gconf remains
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v53
|
v54
|
|
155 | 155 | * `libpurple/protocols/zephyr/zephyr.c` |
156 | 156 | * `gconftool-2` (only on startup) |
157 | | * `pidgin/gtkutils.c` |
| 157 | * `libpurple/proxy.c` |
158 | 158 | |
159 | 159 | === Pidgin's processes === |
… |
… |
|
161 | 161 | A little annotation of processes that Pidgin 3.0 spawns, where, and why. This will help us know where and when to chroot and what might break. |
162 | 162 | |
163 | | * on startup, about twenty processes are spawned for gconftool-2 to register different kinds of URL handlers |
164 | | * I wouldn't be surprised if this significantly delays startup, and if there's a better way to do it |
165 | | * see [https://hg.pidgin.im/soc/2015/mmcc/main/file/bc63cdee394b/pidgin/gtkutils.c#l3441 pidgin/gtkutils.c:3441] |
| 163 | * `gconftool-2` is used to query proxy settings from GNOME |
| 164 | * see [https://hg.pidgin.im/pidgin/main/file/6525f141a8bb/libpurple/proxy.c#l244 libpurple/proxy.c:244] |
166 | 165 | * DNS queries are done from forked processes |
167 | 166 | * these don't seem to use any significant access and could probably be heavily locked down |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!