Thanks Michael,

I had not tried a signal shutdown from the console yet,  so I did and it worked 
fine.     At least I know that RedHat seems to be set up correctly.

However,  if I send a signal from Maint or Operator via 'signal shutdown 
mfsl8009'  linux does not seem to receive the signal.

This makes me think something on the z/VM side is not set up correctly.      
The guest is setup just like the 5.6 guests,  same class,  signal enabled,  but 
the signal doesn't register.

Jim Barnett
z/VM and zLinux 
United Health Technologies
763-744-3066
[email protected]

-----Original Message-----
From: Michael Holzheu [mailto:[email protected]] 
Sent: Friday, August 16, 2013 4:16 AM
To: Linux on 390 Port
Cc: Barnett, James K
Subject: Re: Rhel 6.4 signal shutdown not working.

On Thu, 15 Aug 2013 17:44:16 +0000
"Barnett, James K" <[email protected]> wrote:

> Yup,   s390 tools is installed.     
> 
> I have setup /etc/rc.d/rc.local  as described in the Cookbook to run '  
> chshut halt vmcmd logoff' and 'chshut poff vmcmd logoff ' at boot time. 
> 
> Lsshut shows the following:
> Trigger          Action
> ========================
> Halt             vmcmd ("logoff")
> Power off        vmcmd ("logoff")
> Reboot           reipl
> Restart          stop
> Panic            stop
> 
> 
> But,  I suspect it is something along these lines that is tripping me up.

Hello Jim,

The setting of the shutdown actions should have no effect for signal shutdown.

I tried "signal shutdown" on my development RHEL6.4 system and it worked for me:

$ cat /etc/issue
Red Hat Enterprise Linux Server release 6.4 (Santiago)


$ cat /etc/init/control-alt-delete.conf
# control-alt-delete - emergency keypress handling # # This task is run 
whenever the Control-Alt-Delete key combination is # pressed.  Usually used to 
shut down the machine.
start on control-alt-delete
exec /sbin/shutdown -r now "Control-Alt-Delete pressed"


$ lsshut
Trigger          Action
========================
Halt             vmcmd ("logoff")
Power off        vmcmd ("logoff")
Reboot           reipl
Restart          stop
Panic            stop


#cp signal shutdown within 1
Broadcast message from ...
        (unknown) at 11:08 ...
The system is going down for reboot NOW!
Control-Alt-Delete pressed

.....

Unmounting file systems:  "  OK  ยจ
init: Re-executing /sbin/init...
Please stand by while rebooting the system.....
01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
from CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a 
SIGP stop from CPU 00. 00: HCPGIR450W CP entered; disabled wait PSW 00020001 
80000000 00000000 00000FFF

At the end the magic PSW with address 0xfff is loaded that should signal to 
z/VM that the guest system has stopped.

Michael


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

Reply via email to