Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: File Locking Tricks and Traps

by grantm (Parson)
on Mar 06, 2003 at 07:33 UTC ( #240833=note: print w/ replies, xml ) Need Help??

in reply to File Locking Tricks and Traps

Cool. I've often used flock to ensure only one instance of a program is running, but I never thought of opening $0 and locking that - consequently each of my scripts litters the filesystem with a matching .lck file.

Comment on Re: File Locking Tricks and Traps
Replies are listed 'Best First'.
Re: Re: File Locking Tricks and Traps
by Limbic~Region (Chancellor) on Mar 06, 2003 at 18:02 UTC
    There is a better reason to use $0 then leaving the filesystem littered with lock files. I pointed out to Nitrox here that in Unix, it is possible to delete a locked file, and that he should use the process table or semaphores instead. He wanted to know if there was a way around this, and I replied with this, which is an attempt at security through obscurity.

    What Dominus is doing is beautiful. By locking $0, it can't be deleted - or rather it can be, but then there wouldn't be a program to run Dominus++.

    Cheers - L~R

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://240833]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (13)
As of 2016-05-26 18:57 GMT
Find Nodes?
    Voting Booth?