From: Randy Dunlap <rdunlap@infradead.org>
To: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: do not suspend/sleep
Date: Mon, 1 Feb 2021 15:47:29 -0800 [thread overview]
Message-ID: <f4cfa048-f612-8e38-2899-988471d84faa@infradead.org> (raw)
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.
I was considering a way to generate a fake kbd or mouse input every
M (e.g. 29) minutes.
If that is feasible, what would someone suggest to use here?
(I can script the "wait M minutes" part :) Just need the "how to
inject a keystroke or mouse input" part.)
My first idea was some way to prevent suspend/sleep if the system load
level is > N (e.g. 4 -- user input), but I don't know where to do that.
thanks for any suggestions.
--
~Randy
next reply other threads:[~2021-02-01 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 23:47 Randy Dunlap [this message]
2021-02-02 1:51 ` do not suspend/sleep Barnabás Pőcze
2021-02-02 1:53 ` Randy Dunlap
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=f4cfa048-f612-8e38-2899-988471d84faa@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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).