RE: [cobalt-users] pop lock

["Colin J. Raven" <cjraven@xxxxxxxxxxx>]

>Stale lock files are generally the result of a process or connection
>that is abruptly or abnormally terminated, denying the application
>the opportunity to clean up after itself. It's comparable to all the
>~something files left behind when word crashes or the way fsck runs
>when a linux box shuts down without a proper kill signal. In your
>case, a possible adjustment of connecion timeout settings is indicated,
>either on your end or for your users. If it use to run fine, then
>something has probably changed - perhaps your bandwidth aint what she
>used to be - perhaps you've been hacked, though I would think they'd
>get up to plenty more mischief if you had.
>
>I've written a simple Perl script that you can run as a cron
>job that will
>check a supplied list of directories and unlink any files older than a
>specified time or a default of ten minutes. This is precisely
>what this is
>for. Use with caution of course, plenty of caveats in the file so read
>carefully.
>It used to be on CPAN, though I've not updated in over a year
>so maybe not.
>Look for "strip_lock.pl". If you can't find it there, I can
>probably dig up
>a copy for you.
>
>All that said, I'd check those other considerations first as
>they usually
>indicate a wider problem.

Clark;
I went digging for this nifty sounding tool on CPAN....and unfortunately
it's not there any longer. A search on Google came up empty too. (-:
Could you dig up a copy please? This sounds like something every admin
needs up his sleeve for **occasional** use, (although as you said, a
frequent occurrence of stale lock files sure *is* a problem!!)
Regards,
-Colin
--
Colin J. Raven