Adam wrote:
>
> > Patrick M. Hausen wrote:
> > >
> > > > Am 28.04.2019 um 06:41 schrieb Victor Sudakov :
> > > > "if the /etc/rc.shutdown does not terminate within 120 seconds, init
> > will
> > > > terminate it. The timeout can be configured via the sysctl variable
> > > >
On Mon, Apr 29, 2019 at 3:24 AM Victor Sudakov wrote:
> Patrick M. Hausen wrote:
> >
> > > Am 28.04.2019 um 06:41 schrieb Victor Sudakov :
> > > "if the /etc/rc.shutdown does not terminate within 120 seconds, init
> will
> > > terminate it. The timeout can be configured via the sysctl variable
On Sun, Apr 28, 2019 at 7:41 AM Victor Sudakov wrote:
> Can something be done about this? What about CBSD, FreeNAS and other
> more specialized FreeBSD-based systems, what do they do about VM
> shutdown?
>
CBSD offers to reassign these settings during the initialization
process ( as well as
Patrick M. Hausen wrote:
>
> > Am 28.04.2019 um 06:41 schrieb Victor Sudakov :
> > "if the /etc/rc.shutdown does not terminate within 120 seconds, init will
> > terminate it. The timeout can be configured via the sysctl variable
> > kern.init_shutdown_timeout.“
> What’s keeping you from
On 2019-04-29 09:45, Patrick M. Hausen wrote:
What’s keeping you from increasing that timeout for your
particular requirements? IMHO 2 minutes are a reasonable
default for a system that does not run hypervisor VMs -
which is probably the vast majority.
Anyone with the knowledge to implement a
Hi all,
> Am 28.04.2019 um 06:41 schrieb Victor Sudakov :
> "if the /etc/rc.shutdown does not terminate within 120 seconds, init will
> terminate it. The timeout can be configured via the sysctl variable
> kern.init_shutdown_timeout.“
What’s keeping you from increasing that timeout for your
Dear Colleagues,
The shutdown of vm-bhyve (and probably other bhyve-based VM managers) is
commanded by "service vm shutdown." From man init(8) I've learned that
"if the /etc/rc.shutdown does not terminate within 120 seconds, init will
terminate it. The timeout can be configured via the sysctl
