Thanks Iohannes,

will give a try, but anyway it already happened not the first time to me.

Last time I had 3 identical mac minis with the same system image on each. 2 could run the script without problem, but the 3rd did not. The problem is especially with GEM, as in this case I have double lights turned on and everything is too bright.

Anyway, this should work automatically as the installation is permanent in a museum.

Will get back to you soon.

Popesz  

On Tue, Aug 25, 2015 at 11:00 PM, IOhannes m zmölnig <zmoelnig@iem.at> wrote:

On 08/25/2015 10:53 PM, Csaba Láng wrote:
> Dear list,
> is there a way to avoid that a patch which is run from a script either from
> crontab or just autorun from the system runs twice?
> I heard about --no-gui solution, but never managed to use it on Mac.

i don't know how "--no-gui" is supposed to help you here.
it only might obfuscate the fact that two instances are running...


i can think of two simple ways to avoid double runs:
- setup a shared-ressource (a lock-file): when the script starts it
checks for the lock-file; if it is not there, it will create the lock,
launch Pd; once Pd is finished it will remove the lock;
if the lock *is* there, the script will exit immediately.
see flock(1) on linux and shlock(1) on osx.

- stop all running instances of the patch before starting it.
usually you would just do something along the lines of `pkill -KILL pd`,
before starting a new instance of Pd.

fmasdr
IOhannes


_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

-- 
http://www.nimon.org