From nobody Wed Oct 02 11:33:29 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XJXkM29Rzz5YPJT for ; Wed, 02 Oct 2024 11:33:31 +0000 (UTC) (envelope-from des@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XJXkM1Cfbz4T0j; Wed, 2 Oct 2024 11:33:31 +0000 (UTC) (envelope-from des@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727868811; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jLvy+GA3dTQnDvmRPqlhJY76USYThNpzCpWk3lm+xfY=; b=k4mwCVOY+0r/T2y/HBV+lidDGgrxUn811O5jxmOYePEL8wRYa/L0Pu616WakvPVLgjJRXx TWHhEjL2Q/DUG1z5LI1YE5g0w4dH0r8iNvJUAKArPTvZIxb2lntYFzujm+0F4Z078d4bJs m/DA2nmGtjSKDfSxF+NO5pNF3tqg3uooHwa7qAegvZUQ4gwO3kwR9PXuqqxJt0UYmeyNii OqFgn1lg7lAsg4fSmj4rANNSC2l4rnxS6F9HlytVLiOizhgolg2TvjWOe4GTmBHRnGZrYd d1QIyiDlHWNoJbN3ZwumyI3SEljQxRHng3CC/aKXzYs6ihxalNHnuz8P3PIwQg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727868811; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jLvy+GA3dTQnDvmRPqlhJY76USYThNpzCpWk3lm+xfY=; b=SXzh6JVA8m8VJXJ2wdli/1njJZ4Xg2cSGTljYyhqGwRJcwBlkzc4+ahmv0r60rrneZRJMB cMaocGHD7br1eY9d28IpWyhoy9bPE0DfQHl2rd4qhoTBG2E2fhpWVUa7xV+KTcDgn9nAgt 1yw0AdndL1OWL0d9ZBUSKsRifoWXACSSiGhR1yK2C+GbIzHCldvfeMRVq9gISFCHRx4E9G sBROZ7+VwpZg1zgSEhwQZI8GBR0DiOZyqGtBxXXkkyMqotfoqnwJCgFufdqOi0fHAOfYWB /Z70oOWGqIXki9CzUxTthA6DpxMVdLj/oqYVMK1vgTrf+ybqhlovKxp8HlESsA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727868811; a=rsa-sha256; cv=none; b=H43EhLw8129sWhn81ru2IEGqQ/B+qeCQ8q9kZejrbwS/5B+WeZxiVFO0FTiVjjnp3TDBBf yYKQ15/694Ncfytj5EBPo400XvrzqspTOC43hdFaYwerH96N+2WAs7aZFv5eeIWm8g3xTb XcfKfNkbDNYphO6F0EITYUzZfsP6V4lMdVkTX/PljLcdANCfWcCfL4kE2cOeWutEvCkkf0 rh/VWjVK9mpPPg9/8Y1OOh1ZcZS/iQwxZyhrGGypVdpwupa7KFQd0qSd5cZSlhjLzef9L9 K1x6ongLYWnIUI26owttZMs1wmt2iFSwSI6SU20+4tGbEtZWhcN2Vu4ktJDWkg== Received: from ltc.des.dev (unknown [91.174.26.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: des) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XJXkM05lSzJgR; Wed, 2 Oct 2024 11:33:30 +0000 (UTC) (envelope-from des@freebsd.org) Received: by ltc.des.dev (Postfix, from userid 1001) id 75A85BF612; Wed, 02 Oct 2024 13:33:29 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Frank Leonhardt Cc: freebsd-questions@freebsd.org Subject: Re: Stop console going blank (if it is) In-Reply-To: (Frank Leonhardt's message of "Tue, 1 Oct 2024 10:31:55 +0100") References: User-Agent: Gnus/5.13 (Gnus v5.13) Date: Wed, 02 Oct 2024 13:33:29 +0200 Message-ID: <86ldz6wxh2.fsf@ltc.des.dev> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Frank Leonhardt writes: > I've just asked someone to plug in a monitor and send me a photo of > the screen. "It's blank". By default FreeBSD blanks the console after 300 seconds of inactivity. You can disable this by adding `blanktime=3D"NO"` to /etc/rc.conf or /etc/rc.conf.d/syscons. If you can log into the machine remotely, you can unblank it by typing `vidcontrol -t off