inux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Linker
Harley - hlinke
Sent: Wednesday, January 21, 2015 1:27 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session
Paul,
I logged onto a 3270 console for a SLES 12 system and invoked the vi editor. I
Mine also shows dumb.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Vitale,
Joseph
Sent: Wednesday, January 21, 2015 7:01 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session - terminal type?
What is the Terminal
Work 201-395-1509
Cell917-903-0102
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of John
McKown
Sent: Wednesday, January 21, 2015 7:56 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interrupting Linux under z/VM session
On Wed, Jan 21, 2015
Behalf Of Linker
Harley - hlinke
Sent: Wednesday, January 21, 2015 1:27 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session
Paul,
I logged onto a 3270 console for a SLES 12 system and invoked the vi editor. I
was able to terminate the vi session by entering
¬c
Of
> John McKown
> Sent: Wednesday, January 21, 2015 12:56 PM
> To: LINUX-390@vm.marist.edu
> Subject: Re: Interrupting Linux under z/VM session
>
> On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben wrote:
>
> > On Wed, 21 Jan 2015 12:06:51 +
> > "Beesley
56 PM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session
On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben wrote:
> On Wed, 21 Jan 2015 12:06:51 +
> "Beesley, Paul" wrote:
>
> > Thanks for the tip, I'll try that.
> > Unfortunately it
On Wed, Jan 21, 2015 at 7:09 AM, Beesley, Paul
wrote:
> followed by :q! doesn't work. I can't find anything that does.
> Obviously vi is unique (in many ways ...)
> I don't think you can IPL CMS if you've already booted z/Linux.
>
I was thinking another user in CMS, not IPL'ing CMS in the same
: Interrupting Linux under z/VM session
On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben wrote:
> On Wed, 21 Jan 2015 12:06:51 +
> "Beesley, Paul" wrote:
>
> > Thanks for the tip, I'll try that.
> > Unfortunately it doesn't get me out of my vi sessi
On Wed, Jan 21, 2015 at 6:12 AM, Berthold Gunreben wrote:
> On Wed, 21 Jan 2015 12:06:51 +
> "Beesley, Paul" wrote:
>
> > Thanks for the tip, I'll try that.
> > Unfortunately it doesn't get me out of my vi session. I think I'm
> > stuck there forever
>
> you might want to try
>
> ^z
> killal
: Wednesday, January 21, 2015 11:46 AM
> To: LINUX-390@vm.marist.edu
> Subject: Re: Interrupting Linux under z/VM session
>
> ^c (Shift-6 c) usually sends a Ctrl-C signal, which kills the ping.
>
> -Mike MacIsaac
>
> On Wed, Jan 21, 2015 at 6:38 AM, Beesley, Paul
> wrote
nux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Michael
MacIsaac
Sent: Wednesday, January 21, 2015 11:46 AM
To: LINUX-390@vm.marist.edu
Subject: Re: Interrupting Linux under z/VM session
^c (Shift-6 c) usually sends a Ctrl-C signal, which kills the ping.
-Mike MacIsaac
On Wed, Jan 2
^c (Shift-6 c) usually sends a Ctrl-C signal, which kills the ping.
-Mike MacIsaac
On Wed, Jan 21, 2015 at 6:38 AM, Beesley, Paul
wrote:
> Hi
>
> We are running SLES10 under z/VM.
> At the weekend, I logged onto the Linux guest via a z/VM 3270 session, and
> made the mistake of entering a P
Hi
We are running SLES10 under z/VM.
At the weekend, I logged onto the Linux guest via a z/VM 3270 session, and made
the mistake of entering a PING command with no count parameter so it just
PINGed forever.
I have no SSH access so was unable to logon anywhere else to kill the process.
Eventuall
13 matches
Mail list logo