I created a post commit change trigger on /cinnamon/connect. There is a user changetrigger configured to not activate triggers.
When the change trigger service starts, it logs on to the server. This already triggers the connect trigger which fails, because the trigger is just starting up.
I wasn't able to test whether this was only true for the connect trigger, but I can imagine it is, because it is a special situation.
The server should establish the session and then call the trigger only if the associated user is set to activate triggers. The way it is now, the connect trigger is obviously not practically usable.
I created a post commit change trigger on
/cinnamon/connect
. There is a userchangetrigger
configured to not activate triggers.When the change trigger service starts, it logs on to the server. This already triggers the connect trigger which fails, because the trigger is just starting up.
I wasn't able to test whether this was only true for the connect trigger, but I can imagine it is, because it is a special situation.
The server should establish the session and then call the trigger only if the associated user is set to activate triggers. The way it is now, the connect trigger is obviously not practically usable.