TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. william siqueira
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 4
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by william siqueira

    • william siqueiraW

      Compatibility with Debian 12

      General Discussion
      • • • william siqueira
      4
      0
      Votes
      4
      Posts
      145
      Views

      RussR

      @william-siqueira, thank you for the screenshots. That helps.

      Notice the data folder for the background agent is in root's home folder, not your williams user.

      /root/.TRIGGERcmdData

      I also see No token exists. Login to request one. So you can probably fix it if you run:

      sudo su - triggercmdagent --console (paste in your token)

      Or you could copy your /home/william/.TRIGGERcmdData folder to /root/.TRIGGERcmdData so it won't create a second computer in your account because you already have a computerid.cfg file in /home/william/.TRIGGERcmdData and the background agent that will run as root will use that computer id.

    • william siqueiraW

      Compatibility with Debian 12

      General Discussion
      • • • william siqueira
      4
      0
      Votes
      4
      Posts
      117
      Views

      RussR

      @william-siqueira, first you could make sure the default commands you have in your commands.json run when you click the green Trigger button in your account.

      The background commands (the commands with ground = background) will run if you've installed the background service using installdaemon.sh, but you'll need to use ps -ef to check whether they ran because they don't run in the foreground where you can see them.

      After that, you can add your own commands by copying one of those lines, and editing the command field to be your own command.