<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Multiple Users - One RPi]]></title><description><![CDATA[<p dir="auto">Can I use one Raspberry Pi setup and use multiple users? (Me and my Wife?)</p>
<p dir="auto">How do I go about that?</p>
]]></description><link>https://www.triggercmd.com/forum/topic/358/multiple-users-one-rpi</link><generator>RSS for Node</generator><lastBuildDate>Thu, 18 Jun 2026 07:58:44 GMT</lastBuildDate><atom:link href="https://www.triggercmd.com/forum/topic/358.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 10 Jan 2019 07:30:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Multiple Users - One RPi on Fri, 11 Jan 2019 00:14:20 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://www.triggercmd.com/forum/uid/1743">@atmosphere</a>, I'm sorry but right now the TRIGGERcmd installer only supports one TRIGGERcmd account per Raspberry Pi.</p>
<p dir="auto">But, theoretically you could maybe run two instances of the TRIGGERcmd agent on the Pi, as two separate Linux users, and give those two users sudo access if they need to run things as root.</p>
<p dir="auto">If you run triggercmdagent --console it will run in foreground mode like so, and store two separate commands.json files in the .TRIGGERcmdData subfolder of their respective home folders:</p>
<pre><code>pi@raspberrypi:~ $ triggercmdagent --console
Run installdaemon.sh to install the triggercmdagent daemon so it runs during boot
Daemon install: false
No token exists.  Login to request one.
prompt: token:
</code></pre>
<p dir="auto">The trick would be in getting the two agents to run after a reboot.</p>
]]></description><link>https://www.triggercmd.com/forum/post/1159</link><guid isPermaLink="true">https://www.triggercmd.com/forum/post/1159</guid><dc:creator><![CDATA[Russ]]></dc:creator><pubDate>Fri, 11 Jan 2019 00:14:20 GMT</pubDate></item></channel></rss>