lockfiles

[William J. McEachran]

The issue disappeared  ( 'lockfiles' were being left "locked").
I don't think I was getting the full story (working remotely) from the
client.  Something else was going on over there which I'll never
about.
Thanks all


On Wed, Mar 21, 2012 at 5:41 PM, Kenneth Brody <kenbrody at spamcop.net> wrote:
> On 3/21/2012 12:18 PM, William J. McEachran wrote:
>>
>> I'm seeing lockfiles left after a demand index is rebuilt on an old system
>> recently moved from SCO-Unix to Linux.
>> Any ideas why the lockfiles aren't being cleaned up?
>
>
> Define "aren't being cleaned up".
>
> What error(s) are you getting?
>
>
>> 'dxmaint --ver' is 5.7.00D4
>>
>> It's perms are:
>> -rwsr-xr-x 1 filepro daemon 613628 May 31  2011 dxmaint
>>
>> In fact, as I look at the system it seems to be generating, and leaving a
>> lot of lockfiles with no development working occuring.
>
>
> Ah...  You seem to think that the mere existence of a lockfile is a problem.
>  Unless there is something wrong with the *contents* of the lockfile (which
> should be all zeros if no one is accessing the file), there is nothing wrong
> with a lockfile existing.  In fact, if you went into a file and a lockfile
> *weren't* generated, it would mean something is seriously wrong.
>
>
>> This is on openSUSE 11.4
>
>
> --
> Kenneth Brody



-- 
Bill McEachran
bill.mceachran at gmail.com     http://www.wjmceachran.com