Re^3: how to exit if tool is already running

JavaFan, I know we have had this discussion before, but the question says:

I have written a small Tool in perl. ... Sometimes accidentally we clicked twice the tool. (emphasis mine)

Given this, the complaint about an atomic procedure seems somewhat pedantic for a small (probably Q&D) tool.

Furthermore, you have a problem if the program dies and doesn't get the chance to clean up the special file.

Can be handled by either an exit handler or checking to see if the program is already running.

Or if something else removes the file.

Write and/or exclusive locks handle this.

Even if it is not how you would do it (possibly for a full blown application), it may well fit the bill for this task.

Comment on Re^3: how to exit if tool is already running

Replies are listed 'Best First'.
Re^4: how to exit if tool is already running by JavaFan (Canon) on Aug 13, 2010 at 14:03 UTC
Furthermore, you have a problem if the program dies and doesn't get the chance to clean up the special file. Can be handled by either an exit handler But they aren't always called, are they? The OS may crash. Something could kill it with SIGKILL. The application may `exec`. checking to see if the program is already running. Write and/or exclusive locks handle this. So, now we're down to using external files, exit handlers, checking the process table, and using locks (which doesn't prevent a `rm` of the file). Even if it is not how you would do it (possibly for a full blown application), it may well fit the bill for this task. Or it may not. It sure ain't any simpler than `use Fcntl ':flock'; flock DATA, LOCK_EX\|LOCK_UN or exit;` [download] which doesn't require exit handlers, external files, does the right thing when the program exits unexpectedly, and doesn't have to check to process table. Now, I'm not claiming it isn't possible. I'm disagreeing with you that it's the easiest solution. Self-locking is easier than external locking.	[reply] [d/l]

Replies are listed 'Best First'.

Re^4: how to exit if tool is already running
by JavaFan (Canon) on Aug 13, 2010 at 14:03 UTC

Furthermore, you have a problem if the program dies and doesn't get the chance to clean up the special file.
Can be handled by either an exit handler

exec

checking to see if the program is already running.
Write and/or exclusive locks handle this.

rm

Even if it is not how you would do it (possibly for a full blown application), it may well fit the bill for this task.

use Fcntl ':flock';
flock DATA, LOCK_EX|LOCK_UN or exit;
[download]

Now, I'm not claiming it isn't possible. I'm disagreeing with you that it's the easiest solution. Self-locking is easier than external locking.

[reply]
[d/l]