comment on

Nitrox,
Not that I know of. There are things you can do to reduce the probability that the file will be accidentally deleted - security through obscurity. These things include:

Changing the directory where the file resides permissions to 000.

Use non-typical characters in the file name such as a space, asterick, or worse.

Use alarm for the original script to check if the file has been deleted and re-create. * This requires a lot of overhead to try and compete with the race condition.

Use hard links (not symbolic) so that more than one file combined equal your lock file

Even with these suggestions, there is not the 100% guarantee. Sometimes you need decide that the probability is an acceptable risk and move on. If you are totally against checking the process table - semaphores may be the way to go.

Cheers - L~R

In reply to Re: Re: Re: Re: Re: Determine if script is already running by Limbic~Region
in thread Determine if script is already running by Nitrox

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks