Thanks a lot !
Gerard MONTELEONE
Ingenieur Systeme & Reseau
( 04.95.23.68.09 / 06.87.72.70.32
S.I.TE.C zi du Vazzio
20090 AJACCIO Cedex
[EMAIL PROTECTED]
-----Message d'origine-----
De : Linux on 390 Port [mailto:[EMAIL PROTECTED] De la part de
Malcolm Beattie
Envoyé : mardi 25 novembre 2003 12:01
À : [EMAIL PROTECTED]
Objet : Re: RE : signal shutdown
Monteleone writes:
> This is what i get when i run bootshell
>
> lnxtrs7 login: /sbin/bootshell: /sbin/bootshell: cannot execute binary
> file
[...]
> - run gcc -c ./bootshell-1.3.cc -o /sbin/bootshell
[...]
The "-c" option produces an object file, not an executable. Leave
out the "-c" option and gcc will also do the link stage and create
an executable for you.
Another option for consideration may be the ext_int kernel module
I wrote which lets you trap the external interrupt number of your
choice and have it deliver a signal of your choice to the PID of your
choice. I used that when doing the Large Scale Linux Deployment
redbook to be able to trigger a remote shutdown of a Linux guest
before the SIGNAL SHUTDOWN support was widely available. See
section 9.8 of that redbook for details. Using it to trigger a
shutdown is nice and simple since you only need to deliver a SIGINT
(signal 2) to init (PID 1) and init will then do the ctrlaltdel line
in your /etc/inittab (similar to how the SIGNAL SHUTDOWN does it,
except that that communicates extra data (timeout info) out of band
rather than just being the external interrupt).
--Malcolm
--
Malcolm Beattie <[EMAIL PROTECTED]>
Linux Technical Consultant
IBM EMEA Enterprise Server Group...
...from home, speaking only for myself
