> 2) For situations where this it not possible (e.g. Busybox ash) I used > a simple start wrapper to unblock signals.
I'm curious: how come your process 1 ash had blocked signals ? Process 1 is launched by the kernel, and I haven't heard of a case where the kernel blocks signals before doing so. Or was it maybe something in your linuxrc blocking signals and failing to unblock them ? -- Laurent _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
