The Indigo Server is running under a separate user account (indigo), and the permissions have been set accordingly.
When I start the server, this is what I get in the log:
- Code: Select all
2017-01-01 22:58:40.702 Application Starting Indigo Server version 7.0.2 (Mac OS X 10.12)
2017-01-01 22:58:40.702 Application Loading attachments
2017-01-01 22:58:40.703 Application "device target attachment.scpt" script loaded
2017-01-01 22:58:40.704 Application "group target attachment.scpt" script loaded
2017-01-01 22:58:40.706 Application "growl attachment.scpt" script loaded
2017-01-01 22:58:40.710 Application "iTunes attachment.scpt" script loaded
2017-01-01 22:58:40.712 Application "scenes attachment.scpt" script loaded
2017-01-01 22:58:40.714 Application "time stamp attachment.scpt" script loaded
...but when I switch permissions to my user account and run a local server using Indigo on my user account, or run as a single application, I see this:
- Code: Select all
2017-01-01 23:03:10.578 Application Starting Indigo Server version 7.0.2 (Mac OS X 10.12)
2017-01-01 23:03:10.579 Application Loading attachments
2017-01-01 23:03:10.580 Application "device target attachment.scpt" script loaded
2017-01-01 23:03:10.581 Application "group target attachment.scpt" script loaded
2017-01-01 23:03:10.583 Application "growl attachment.scpt" script loaded
2017-01-01 23:03:10.587 Application "iTunes attachment.scpt" script loaded
2017-01-01 23:03:10.589 Application "scenes attachment.scpt" script loaded
2017-01-01 23:03:10.590 Application "time stamp attachment.scpt" script loaded
[b]2017-01-01 23:03:10.649 Application Loading database "/Library/Application Support/Perceptive Automation/Indigo 7/Databases/Our House.indiDb"[/b]
2017-01-01 23:03:11.031 Application Loading plugin "Action Collection 2.0.4"
2017-01-01 23:03:11.032 Application Starting plugin "Action Collection 2.0.4" (pid 5861)
2017-01-01 23:03:11.033 Application Loading interface "INSTEON Commands 2.0.10"
2017-01-01 23:03:11.034 Application Starting interface "INSTEON Commands 2.0.10" (pid 5862)
The difference is that Indigo Server loads the database just fine when running under my account via Indigo, but I have issues running under a separate account. The database is in the same install directory as Indigo, and the permissions correspond to the rest of the Indigo installation — i.e., when I try to run as a daemon, the DB is "owned" by indigo and has r/w permissions by that user/group.
Is there something obvious that I'm doing wrong? Is there an easy way to force Indigo to link to the proper database, if it's not behind the scenes in the server?
Thanks,
-Greg