Re: [Tutor] Watch and control access to an executable

2006-04-08 Thread Bill Burns
[Bill] >> If I'm not mistaken (and I certainly could be) I believe this recipe >> is used to control instances of an already running *script*. While I'm >> trying to control a completely different executable (program) written >> by someone else. [Alan] > Nope, its si8mply creating an arbitrary

Re: [Tutor] Watch and control access to an executable

2006-04-08 Thread Alan Gauld
> If I'm not mistaken (and I certainly could be) I believe this recipe is > used to control instances of an already running *script*. While I'm > trying to control a completely different executable (program) written by > someone else. Nope, its si8mply creating an arbitrary Mutex, which is like

Re: [Tutor] Watch and control access to an executable

2006-04-08 Thread Bill Burns
[Bill] >>>Desktop to the executable). The problem is, only *one* person at a time >>>should run the program. > [Snip some good advise about file problems (that I'll look in to)] [André] > However, there is a Cookbook solution that does, I believe, that what > the original poster asked: > http://

Re: [Tutor] Watch and control access to an executable

2006-04-08 Thread Bill Burns
[Bill] >> Desktop to the executable). The problem is, only *one* person at a time >> should run the program. > [Alan] > The usual way of doing this is simply to create an empty file > when the program starts and delete it when the program closes > In python: > > ## > # File : exRun.p

Re: [Tutor] Watch and control access to an executable

2006-04-08 Thread Alan Gauld
> > The usual way of doing this is simply to create an empty file > > when the program starts and delete it when the program closes > Couldn't this approach cause problems if the Python program crashes, > leaving behind the empty file? Yes, but its very easy for the administrator to delete the ro

Re: [Tutor] Watch and control access to an executable

2006-04-08 Thread Andre Roberge
On 4/8/06, Alan Gauld <[EMAIL PROTECTED]> wrote: > > Desktop to the executable). The problem is, only *one* person at a time > > should run the program. [snip] > > The usual way of doing this is simply to create an empty file > when the program starts and delete it when the program closes > In pyt

Re: [Tutor] Watch and control access to an executable

2006-04-08 Thread Alan Gauld
> Desktop to the executable). The problem is, only *one* person at a time > should run the program. > Now here's my solution: > 1. Create a program let's call it 'myProg' that spawns 'otherProg'. > 2. 'myProg' will utilize a config file. > 3. When 'myProg' is started it looks in the config file t