On Sun, Jun 15, 2014 at 10:12:14PM +0200, Jim Klimov wrote:
> On 2014-06-15 15:01, Gary Mills wrote:
> >
> >What you need here is a remote console.
>
> That's for sure, in general.
>
> But on this box it does not have telnet (or rather, it has either
> telnet or ssh - but not both at the same tim
On 2014-06-15 14:42, Oscar del Rio wrote:
On 14/06/2014 6:09 PM, Jim Klimov wrote:
an interesting puzzle came up: how can one define an SMF service
so that it would ignore the system-wide shutdown and would only
(perhaps ungracefully) die off when the kernel/zone goes down?
Perhaps a service
On 2014-06-15 15:01, Gary Mills wrote:
On Sun, Jun 15, 2014 at 12:09:09AM +0200, Jim Klimov wrote:
For a practical use-case, consider an SSH or Telnet service that
is used for remote management of the box. The shutdown procedure
may stall for a number of reasons. An admin wants to intervene
for
On Sun, Jun 15, 2014 at 12:09:09AM +0200, Jim Klimov wrote:
>
> For a practical use-case, consider an SSH or Telnet service that
> is used for remote management of the box. The shutdown procedure
> may stall for a number of reasons. An admin wants to intervene
> for investigation or to force a rud
On 14/06/2014 6:09 PM, Jim Klimov wrote:
an interesting puzzle came up: how can one define an SMF service
so that it would ignore the system-wide shutdown and would only
(perhaps ungracefully) die off when the kernel/zone goes down?
As an example, I have this somewhat implemented with an SVR4
in
Hi,
an interesting puzzle came up: how can one define an SMF service
so that it would ignore the system-wide shutdown and would only
(perhaps ungracefully) die off when the kernel/zone goes down?
For a practical use-case, consider an SSH or Telnet service that
is used for remote management of th
