Re: Calling system(3) when SIGCHLD is SIG_IGN'd

--eeRmVoB5WImNcgBY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

There seems to be only a single fork() in ctwm anyway, to call m4 to
parse the config file. The SIGCHLD changing could be limited to that
area, then set back to default.

Or, alternatively, a proper signal handler for SIGCHLD could be set up.

-Olaf.
--=20
___ Olaf 'Rhialto' Seibert                            <rhialto/at/falu.nl>
\X/ There is no AI. There is just someone else's work.           --I. Rose

--eeRmVoB5WImNcgBY
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEFVAhiiWjqgwBVdQAmYnGRWHD+9MFAmTXh7AACgkQmYnGRWHD
+9OYGAf+IKHNtiVkloCXy/YweKqqw0ypqVH/PjMvyLx9LxtlYeGDGrH8zbbrf5If
rnKIcLYD9HgxMxoVayrOSC/RdXlFyzsLHrWajQwW0HFXQ+AjjFmUoGsQuGWYHe0x
8JUsgrW5iKCRLaKdXZC3Q+enXVJoxwRbRPFM9P8VV8g31D8Kqhzqpho7gBMvWg0x
/Dz4FbXH7bV0+NpAcVJOkVaozTIZtc344lsmEYQAOxB7XGHLExbmZBbWf4raSegE
4kZI2iK32SKXmAjmsE+3XVnr/jhAJmHVx/o4LhqcFLc5JVnrS7XGCuMjUvqXubd0
zi240vWIFKqmxj/nAWDcgz3HtsSwMw==
=VGTa
-----END PGP SIGNATURE-----

--eeRmVoB5WImNcgBY--