Hi,
you can setup ad-hoc override for ssh, so the escape would be sent to zlogin or
you can send ~~. to send it to the "inner session". If you overdo it with the
tildes, just press enter and try again with one less.
override the escape sequence for ssh (man ssh):
-e escape_char
4 января 2016 г. 14:48:11 CET, Dan McDonald пишет:
>
>> On Dec 31, 2015, at 10:45 AM, Bob Friesenhahn
> wrote:
>>
>> I am accessing the system via ssh which uses '~.' to terminate the
>ssh session. This is also the default shutdown sequence for 'zlogin
>-C'. The idea is that after doing some ini
On Mon, 4 Jan 2016, Dan McDonald wrote:
On Dec 31, 2015, at 10:45 AM, Bob Friesenhahn
wrote:
I am accessing the system via ssh which uses '~.' to terminate the ssh session. This is
also the default shutdown sequence for 'zlogin -C'. The idea is that after doing some
initial administratio
> On Dec 31, 2015, at 10:45 AM, Bob Friesenhahn
> wrote:
>
> I am accessing the system via ssh which uses '~.' to terminate the ssh
> session. This is also the default shutdown sequence for 'zlogin -C'. The
> idea is that after doing some initial administration using 'zlogin -C', the
> "~."
You can work round this by escaping the '~' character. Try typing '~~.'
to exit from 'zlogin -C'. Here's the relevant section from the ssh man
page:
> A single tilde character can be sent as ~~, or by following the tilde
> with a character other than those described above. The escape character
I would like to share a idea regarding how the newly created zone
may have difficulties shutting down.
I am accessing the system via ssh which uses '~.' to terminate the ssh
session. This is also the default shutdown sequence for 'zlogin -C'.
The idea is that after doing some initial administ
Dan,
I remember that in my cases when a zone shutdown got stuck, "zoneadm
list -cv" showed the state of the hung zone as: shutting_down
On 12/22/2015 02:02 AM, Dan McDonald wrote:
I forgot to mention "zoneadm list -cv". That would've shown the zone's state.
The pstack for zoneadmd showed t
I forgot to mention "zoneadm list -cv". That would've shown the zone's state.
The pstack for zoneadmd showed this function:
http://src.illumos.org/source/xref/illumos-gate/usr/src/cmd/zoneadmd/zoneadmd.c#1089
is waiting for something to only exit a loop after a long wait.
I'm curious which of:
Have others encountered this issue? What can be done to fix it?
This message is printed by zoneadmd. If you or anyone else encounters this
hang again, please do the following:
1.) While zoneadm is hung, check the console for the above message, you'll see
a pid for zoneadmd (Bob's example
> On Dec 6, 2015, at 7:19 PM, Bob Friesenhahn
> wrote:
>
> On a freshly installed zone with no additional packages installed (but with
> one lofs mount to a filesystem), I am seeing a glitch with 'zoneadm -z name
> shutdown', 'zoneadm -z name reboot' or 'reboot' within the zone. This
> mess
when this occured for the
first time but it might be after upgrading to r16.
> Gesendet: Montag, 07. Dezember 2015 um 01:19 Uhr
> Von: "Bob Friesenhahn"
> An: omnios-discuss@lists.omniti.com
> Betreff: [OmniOS-discuss] OmniOS r151016 zone has difficulties shutting down
On a freshly installed zone with no additional packages installed (but
with one lofs mount to a filesystem), I am seeing a glitch with
'zoneadm -z name shutdown', 'zoneadm -z name reboot' or 'reboot'
within the zone. This message appears on the console and in the
/var/adm/messages file of the
12 matches
Mail list logo
