On Fri, 12 Jun 2015 20:06:40 -0300
Guillermo wrote:
> 2015-06-12 9:44 GMT-03:00 Steve Litt:
> > On Fri, 12 Jun 2015 11:31:44 +0200 Laurent Bercot wrote:
> >
> >> Well, your host system will definitely catch the 3 finger
> >> salute; it won't be sent as is to your guest system. Is there a
> >>
2015-06-12 9:44 GMT-03:00 Steve Litt:
> On Fri, 12 Jun 2015 11:31:44 +0200 Laurent Bercot wrote:
>
>> Well, your host system will definitely catch the 3 finger salute; it
>> won't be sent as is to your guest system. Is there a way for the VM to
>> send an emulated ctrl-alt-del press to the guest
On Fri, 12 Jun 2015 11:31:44 +0200
Laurent Bercot wrote:
> On 12/06/2015 02:54, Steve Litt wrote:
> > * Whole thing running in a VirtualBox VM
>
> Ah, I'm not sure how all this plays with virtualization. VirtualBox
> looks like a full virtualizer with a separate kernel for the guest,
> so it p
On 12/06/2015 02:54, Steve Litt wrote:
* Whole thing running in a VirtualBox VM
Ah, I'm not sure how all this plays with virtualization. VirtualBox
looks like a full virtualizer with a separate kernel for the guest,
so it probably makes no difference, but if your guest kernel is also
your host
On Fri, 12 Jun 2015 02:35:28 +0200
Laurent Bercot wrote:
> There was a time where the kernel protected pid 1 against signals
> sent by user processes, and only sent it signals it generated itself
> such as SIGINT for Ctrl-Alt-Del. This is the reason why sysvinit
> uses /dev/initctl as a communi
On Fri, 12 Jun 2015 00:56:54 +0200
Laurent Bercot wrote:
> It's Complicated (TM).
>
> First, you're not supposed to be able to send signals to process 1.
> Only the kernel can do that. So I'm surprised you managed to get it
> to work with a kill command, and I'm interested in the details.
On 12/06/2015 01:10, post-sysv wrote:
Not sure what you meant by this statement, but you certainly can
provided PID1 has set explicit signal handlers.
Then it changed at some point. (I just tested to be sure, and I was
able to send a signal to my pid 1 indeed, on Linux 3.19.1.)
There was a t
Not sure what you meant by this statement, but you certainly can
provided PID1 has set explicit signal handlers. This is typically to
implement global system state events like SAK, emergency and rescue
shell transitions and indeed often the shutdown procedure.
On 06/11/2015 06:56 PM, Laurent B
On 11/06/2015 23:34, Steve Litt wrote:
I have a feeling that SIGINT isn't getting all the way to PID1. When I
do the following:
kill -s SIGINT 1
It runs rc.shutdown with the argument "reboot" and reboots the system,
just like it's supposed to. But when I press Ctrl+Alt+Del at a virtual
terminal
all,
> > What interrupt does Ctrl+Alt+Delete send PID1?
> > Google just tells how to tweak /etc/inittab to react to
> > Ctrl+Alt+Del, but in my case /etc/inittab isn't being used: I need
> > to react to the specific interrupt.
> > Thanks,
> > SteveT
On Thu, 11 Jun 2015 10:04:13 -0700 (PDT)
"Robert Hencke" wrote:
> On Thu, Jun 11, 2015 at 12:59 PM, Steve Litt
> wrote:
>
> > Hi all,
> > What interrupt does Ctrl+Alt+Delete send PID1?
> > Google just tells how to tweak /etc/inittab to react to
> >
I believe this is SIGINT.
On Thu, Jun 11, 2015 at 12:59 PM, Steve Litt
wrote:
> Hi all,
> What interrupt does Ctrl+Alt+Delete send PID1?
> Google just tells how to tweak /etc/inittab to react to Ctrl+Alt+Del,
> but in my case /etc/inittab isn't being used: I need to react
Hi all,
What interrupt does Ctrl+Alt+Delete send PID1?
Google just tells how to tweak /etc/inittab to react to Ctrl+Alt+Del,
but in my case /etc/inittab isn't being used: I need to react to the
specific interrupt.
Thanks,
SteveT
Steve Litt
June 2015 featured book: The Key to Eve
13 matches
Mail list logo
