My interest is foremost trivial. Not necessarily related to the
application of such interrupts.
Nevertheless, with regards to the post:
* runscripts can (and AFAIK do) trap and handle SIGINT.
* the interactive mode is ok for interrupting the init process between
scripts. But I can't interrupt a script while it's running with 'I', and
with SIGINT, I can.
Amit
Renat Golubchyk wrote:
On Fri, 20 Nov 2009 00:02:47 +0200 Amit Dor-Shifer <ami...@oversi.com>
wrote:
When hitting Ctrl-C during startup, I manage to interrupt services at
the early stages of init, yet later-on I can no-longer do this. It
seems that up till runlevel 'default', services can be hit with the
interrupt.
Why do you want to stop services by hitting CTRL-C ? Services are
shell scripts. Hitting CTRL-C stops the script somewhere in the
middle during its execution. Everything that was done until that moment
won't be automagically undone. There can be files left , and processes
already started will still run. That's not clean.
Better use the interactive init feature. Just hit 'I' when init starts
(init even tells you, that you can do it) and choose which services to
start by hitting 'y' and 'n'.
Cheers,
Renat
