forgive me if I keep hammering on this topic, but i'm still not able to get this to work. I'm trying to get Linux guests to respond to the CP SIGNAL SHUTDOWN command.
Using SuSE SLES7 (2.4.7 kernel. This was downloaded from SuSE's site as k-timer-2.4.7-20030221, dated Feb 21 2003. Should have all the latest stuff, no?) z/VM 4.3.0 I set up the line in /etc/inittab ca:12345:ctrlaltdel:/sbin/shutdown -t1 -h now I even placed the following in the server's CP directory entry, even though it should not be needed: IUCV *SIGNAL When the server logs on , I issue the command in its PROFILE EXEC: 'CP SET SIGNAL SHUTDOWN 60' which it accepts with no problem. With the Linux server up, I issue the following command from a privileged CMS account: CP SIGNAL SHUTDOWN LINUXSRV WITHIN 60 and get the message HCPSIG2110E User LINUXSRV is not enabled for signals Ready(02110); I know I'm missing something. Can someone tell me what? They say there are three signs of stress in your life. You eat too much junk food, you drive too fast and you veg out in front of the TV. Who are they kidding? That sounds like a perfect day to me! Gordon Wolfe, Ph.D. (425)865-5940 VM & Linux Servers and Storage, The Boeing Company > ---------- > From: Ferguson, Neale > Reply To: Linux on 390 Port > Sent: Monday, March 24, 2003 9:23 AM > To: [EMAIL PROTECTED] > Subject: Re: CP Signal shutdown requirements > > They later kernels from SuSE have the patch in it. My patch has been adapted > by the kernel folks so that it's different to the quiesce-diffs you've > located. SLES8 definitely has it. You'll need to update /etc/inittab to > enable the signal to do the ctrl-alt-del processing. > > -----Original Message----- > I see that Neale has a patch called linux-2.4.7-s390-quiesce.diffs which > appears to be a patch on smp.c for SLES7. In order to apply this patch, do > I have to completely regen the kernel? I'm reluctant to start down that long > learning curve at this time. Or does SuSE or anyone else have a downloadable > 2.4.7 kernel with the SIGNAL enablement already installed? Or should I just > wait for SLES8 to be delivered? (We ordered it in December. No idea what > the holdup is.) Is SIGNAL enabled in SLES8 even? > >
