Limiting the number of instances of one application

[fullmetalcoder]

I'm trying to limit the number of running instances of an application, which is mostly useful when dealing with file registration...

I've had a quick look at Assistant which seems to use a client/server architecture to achieve that (through QTcpSocket if I remember well) and I didn't understand how it worked... Any explanation ?

[e8johan]

There is a Qt solution for this... and KDE does it (I seem to recall). Perhaps you can find simple solutions there...

[Mike]

Well you could use a computer resource like a socket - you suggested that already. Pick a range of e.g. 5 sockets that your app would try to open. maybe 40000...40004. When your app is starting it will try to open such a socket. If it fails it will open the next in that range. If no socket in that range is available then your app would not start. Maybe you even enhance the socket logic that way, that you can send a simple command to it and wait for a known response. If that response doesn't come, then you know it's not your app, but the app from somebody else...
Does this make sense?
If sockets is not what you want to use, you may create something else like a named message queue or pipe... or a kernel mutex etc... there are several solutions to this...

[Valheru]

Isn't this what DCOP is for in KDE? Don't know what Windows uses or if Qt has it's own abstraction for handling stuff like this.

[fullmetalcoder]

Well you could use a computer resource like a socket - you suggested that already. Pick a range of e.g. 5 sockets that your app would try to open. maybe 40000...40004. When your app is starting it will try to open such a socket. If it fails it will open the next in that range. If no socket in that range is available then your app would not start. Maybe you even enhance the socket logic that way, that you can send a simple command to it and wait for a known response. If that response doesn't come, then you know it's not your app, but the app from somebody else...
Does this make sense?
If sockets is not what you want to use, you may create something else like a named message queue or pipe... or a kernel mutex etc... there are several solutions to this...

There are two problems : I don't have any experience of socket programming and I want a cross-platform solution.
Moreover I don't think I have enough time to search for that feature into the whole KDE sources and then port that Qt3 (and maybe KDE kernel)-dependent code to plain and portable Qt4.
You talked about "socket ranges", could you explain that to me alittle deeper? As I said I'm a noob in socket-programming...

[nouknouk]

Hi,

for registered customers, there is a special class to ensure only one instance of your application is running : QtSingleApplication (it exists for both Qt3 and Qt4 versions).

This class is unfortunately unavailable for open-source licensee :-/

[fullmetalcoder]

This class is unfortunately unavailable for open-source licensee :-/

Unfortunately my software is meant to be Open Source thus compilable against Qt Open source so I can't rely on something like this. Neither can I "steal" its code so I'm looking for an equivalent solution in plain cross-platform and open source Qt 4. If you've heard about this class maybe you could explain me roughly how it works???

[gfunk]

My guess is that their QtSingleApplication would do something different for each OS, as there's nothing preventing Qt from doing whatever it wants, as long as it achieves the "single app" functionality. In Windows, it can be fairly easily done with their own named pipes or named mutexes (not an option for other os's) - I'm sure other OS's have their own efficient way of accomplishing the "single app".

Using sockets not be very elegant as it pollutes the port number-space, and in the worst case, may have to check several port numbers - but for the end-user, it may still be suitable and sufficiently portable.

[nouknouk]

Hi,

about general concepts of QtSingleApplication, there are 3 different ways the mutex is implemented, depending on the OS used (Win, MacOS, Linux) :

-on windows, the CreateMutex function is used, the time a call to FindWindow is done. If the window is already existing, that means an instance is already started. The mutex is released just after in all cases.

- on linux, the Atom feature is used to implement the mutex. The window is then retrieved with something like findWindow

- on mac ... i don't know

QtsingleApplication gives another feature : the ability to send a message to the already running instance. Usefull, for example, when the second application's instance wants to send a filename to the first one in order to open a document. This mechanism is implemented using platform specific ways to post a message in their event loops.

[fullmetalcoder]

Are "regular" Qt mutexes/threads/... able to perform this task or am I forced to use plenty of dirty platform-dependent code (which I don't know well BTW)?

@nouknouk : you seem to be quite informed about QtSingleAppication. Do you think Trolltech plans to release it under GPL?

[Chicken Blood Machine]

A quick and dirty cross-platform solution would be to create a 'lock' file at startup and delete the file at shutdown. Any new instances check if the file exists first before continuing.

This isn't foolproof, since if your app crashes, you will have to delete the file manually.

[wysota]

This isn't foolproof, since if your app crashes, you will have to delete the file manually.

You can overcome that problem for example by checking if a process which created the file exists (the file can contain the process id of the creator). This still isn't 100% sure, but improves the situation a little.

[fullmetalcoder]

I know I can use process ID under Unix platform but what about others, especially Windows? Actually, even if it's not the most straightforward I think the sockect stuff is the best... I'll try to understand designerassistant sources and, well, we'll see...

[arnaiz]

A quick and dirty cross-platform solution would be to create a 'lock' file at startup and delete the file at shutdown. Any new instances check if the file exists first before continuing.

This isn't foolproof, since if your app crashes, you will have to delete the file manually.

IMO this is the best solution, easy and clean. It works for all platforms, it can be instrumented through the net, or locally, it can be a counter to limit number of applications...

Simple is, in many cases, the best solution...

[wysota]

Simple is, in many cases, the best solution...

It has its strong disadvantages. There is really no way telling if the lock file is stale or not. Under Windows you can easily use a file to make a singleton application by demanding a mandatory lock on the file. On the other hand I don't know if the lock will be released when the app gets killed. So a solution is easy but the drawback is that you might not be able to restart the application after a crash. The same goes with files holding pids of processes. You can never be sure if the lock file is stale or not and eventually you have to guess (for example by trying to find the process in the process table) or ask the user (like for example kmail does). So simple is easy to implement, but can fail as easily.

[nouknouk]

@nouknouk : you seem to be quite informed about QtSingleAppication. Do you think Trolltech plans to release it under GPL?

I only have a licensee version of Qt, nothing more. QtSingleApplication class exists since a while (before Qt 3.3.x) and it is still not licensed under GPL, so I think It won't be available for open source license soon :/

Actually, even if it's not the most straightforward I think the sockect stuff is the best... I'll try to understand designerassistant sources and, well, we'll see...

Another issue with the use of QSocket is that the user may have a firewall that doesn't allow to open listening socket.

[Lawand]

I only have a licensee version of Qt, nothing more. QtSingleApplication class exists since a while (before Qt 3.3.x) and it is still not licensed under GPL, so I think It won't be available for open source license soon :/

FWIW, QtSingleApplication is now available as an Open Source Edition (LGPL) here

[roxton]

Try the SingleApplication library:
http://www.qt-apps.org/content/show....?content=81163