comparison libpurple/example/nullclient.c @ 21060:9838af97586b

A pidgin fans in Great Britain.U.K thinks that nullclient should explicitly ignore SIGCHLD to avoid defunct dns resolution children. Really?

21059:0f4a5ff5dc84

	char *password;
	GMainLoop *loop = g_main_loop_new(NULL, FALSE);
	PurpleAccount *account;
	PurpleSavedStatus *status;

	init_libpurple();

	printf("libpurple initialized.\n");

	iter = purple_plugins_get_protocols();

21060:9838af97586b

	char *password;
	GMainLoop *loop = g_main_loop_new(NULL, FALSE);
	PurpleAccount *account;
	PurpleSavedStatus *status;

	/* libpurple's built-in DNS resolution forks processes to perform
	 * blocking lookups without blocking the main process.  It does not
	 * handle SIGCHLD itself, so if the UI does not you quickly get an army
	 * of zombie subprocesses marching around.
	 */
	signal(SIGCHLD, SIG_IGN);

	init_libpurple();

	printf("libpurple initialized.\n");

	iter = purple_plugins_get_protocols();