I don't think that the rexec daemon needs to be running on z/VM. To have
it start with a Linux SLES7 guest, modify the /etc/inetd.conf file:

exec    stream  tcp     nowait  root    /usr/sbin/tcpd  in.rexecd

.thanks

Scott Archer wrote:
>
> Okay.... I've got the TCP/IP rexec daemon running on z/VM.  Now I'm
> assuming I also have to have a rexec daemon running on my Linux guest.  I'm
> very much a Linux newbie...... How do you start the daemon on the Linux
> side? I've looked in the man pages, but no luck on actually starting it up.
>
> TIA,
>
> Scott
>
> At 09:03 AM 03/25/2003, you wrote:
> >On a related note, you might consider using the rexec command from VM to
> >issue a '/sbin/shutdown -h now' to your Linux guests.
> >.thanks
> >
> >"Wolfe, Gordon W" wrote:
> > >
> > > We've just upgraded to z/VM 4.3 and would like to begin using the CP
> > SIGNAL SHUTDOWN command to shut down our Linux servers.  We are running
> > SuSE SLES7 with the timer patch,and I think I have the latest update.
> > >
> > > When I try the SIGNAL command I get
> > >
> > > HCPSIG2110E User LNX54321 is not enabled for signals
> > > Ready(02110);
> > >
> > > 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?
> > >
> > > 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
>
> **************************************************************************
>   Scott Archer
>
>     Mainframe Systems Administration, New Mexico State University
>     E-mail: [EMAIL PROTECTED]
>     URL: http://sarcher.nmsu.edu
>     Phone: (505)646-6186
> **************************************************************************

Reply via email to