<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=4886&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / I am in need of a particular suspend+lock script]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=4886</link>
		<description><![CDATA[The most recent posts in I am in need of a particular suspend+lock script.]]></description>
		<lastBuildDate>Mon, 14 Feb 2022 04:00:19 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: I am in need of a particular suspend+lock script]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=34645#p34645</link>
			<description><![CDATA[<div class="quotebox"><cite>ralph.ronnquist wrote:</cite><blockquote><div><p>You could maybe you use the <span class="bbc">-killtime</span> and <span class="bbc">-killer</span></p><p>Though I&#039;m not sure what &quot;warn for 30 minutes&quot; means; warn repeatedly for 30 minutes?</p><p>I suppose eg a 5 minute killer could check the time since slock start, and warn or eventually call pm-suspend?</p></div></blockquote></div><p>Basically, after it is locked, it warns for 30 minutes, doesn&#039;t undo the lock and then goes back to waiting 30 minutes over and over again, kind of thing...</p><p>If its ever idle for longer than the duration, it suspends.&#160; and if you bring it back, aka, take it out of suspend and unlock it,</p><p>then it repeats from step 1.</p><p>Btw, by warn, I mean the screen turns a specific color, or a warning message appears with a timer before it suspends.</p><p>Something like that.</p>]]></description>
			<author><![CDATA[dummy@example.com (zapper)]]></author>
			<pubDate>Mon, 14 Feb 2022 04:00:19 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=34645#p34645</guid>
		</item>
		<item>
			<title><![CDATA[Re: I am in need of a particular suspend+lock script]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=34615#p34615</link>
			<description><![CDATA[<p>You could maybe you use the <span class="bbc">-killtime</span> and <span class="bbc">-killer</span></p><p>Though I&#039;m not sure what &quot;warn for 30 minutes&quot; means; warn repeatedly for 30 minutes?</p><p>I suppose eg a 5 minute killer could check the time since slock start, and warn or eventually call pm-suspend?</p>]]></description>
			<author><![CDATA[dummy@example.com (ralph.ronnquist)]]></author>
			<pubDate>Sun, 13 Feb 2022 04:37:33 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=34615#p34615</guid>
		</item>
		<item>
			<title><![CDATA[I am in need of a particular suspend+lock script]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=34612#p34612</link>
			<description><![CDATA[<p>I have a way to deal with root problem aspect... aka doas...</p><p>But yeah,&#160; I wondered if anyone knows how to make a python script that does something similar to the below:</p><p>I know how to do the first part, which is wait 30 minutes, then lock... xautolock + slock makes this possible... <img src="https://dev1galaxy.org/img/smilies/smile.png" width="15" height="15" alt="smile" /></p><p>The second part, I need help with however...</p><p>after it is locked, WARN for 30 minutes, then activate the part that suspends system...</p><p>This I have covered easily however... </p><p>Just part 2 eludes me at this time...</p><p>Btw, I want this to work with Hyperbola. <img src="https://dev1galaxy.org/img/smilies/smile.png" width="15" height="15" alt="smile" /></p><p>I hope that is okay... </p><p>Just to be clear, the 2nd part isn&#039;t an issue probably on Debian based distros anyhow, as far as I know. Just closing the lid seems to do that already.</p>]]></description>
			<author><![CDATA[dummy@example.com (zapper)]]></author>
			<pubDate>Sun, 13 Feb 2022 02:58:54 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=34612#p34612</guid>
		</item>
	</channel>
</rss>
