From: Randy Dunlap <rdunlap@infradead.org>
To: "Barnabás Pőcze" <pobrn@protonmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: do not suspend/sleep
Date: Mon, 1 Feb 2021 17:53:37 -0800 [thread overview]
Message-ID: <521702af-b5af-02a6-d58d-ff1e63d49e1d@infradead.org> (raw)
In-Reply-To: <_fXGHc0QxoA6O5ljZuheCXVM4m0EDO5yDitURpjxeesPWQ-etoD0Im3937FdotSufu1ZRtBaLFFsCzAY2qtNANeP829mo-YbOZhHksxn8HM=@protonmail.com>
On 2/1/21 5:51 PM, Barnabás Pőcze wrote:
> Hi
>
>
> 2021. február 2., kedd 0:47 keltezéssel, Randy Dunlap írta:
>
>> Hi all.
>>
>> I usually run my systems (laptops) so that they will suspend to RAM
>> after 30 or 60 minutes of no use (no input), but when I am building
>> e.g. 3 kernels, that will take more than 30 minutes and I don't want
>> the system to suspend during that time.
>>
>> I was wondering what options are available to prevent entering suspend.
>> I am willing to manually enter a command to make that happen if one
>> is available.
>> [...]
>
> Have you looked at systemd-inhibit(1)?
No, I'm wasn't aware of that, but I'll take a look.
Thanks.
--
~Randy
prev parent reply other threads:[~2021-02-02 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 23:47 do not suspend/sleep Randy Dunlap
2021-02-02 1:51 ` Barnabás Pőcze
2021-02-02 1:53 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521702af-b5af-02a6-d58d-ff1e63d49e1d@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pobrn@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).