Odd Global .lockfile problem (multiple replies)

[Silas Martinez]

Laura Brody wrote:
...
> 
>     What is an empty lockfile? Please describe.
> 
>     What is the exact error message when the problem
> occurs?
Empty lockfile -

shell$ cat lockfile
shell$

The error was indeed a 'someone else is using this file' type error.
> 
>> It doesn't appear to be a simple permissions issue - I've verified 
>> permissions, and had filepro do the same.
> 
> 
>     Do you mean that you ran the setperms script?

Yes, as well as comparing filesystem permissions on the afflicted 
machine to a running machine with similar user configuration.
> 
> 
>     You trained them right from the begining - excellent!
I'm not a terribly experienced fp admin, but I /do/ know unix/linux. :)
>     Please don't just check them. Get everyone out, then delete
> the lockfiles for all filePro files. BTW, how do you delete the
> lockfiles? ddir? rm .lockfile? some other method?
Indeed, rm lockfile. *sigh*
> 
>     Very, very few people know everything that they need to
> know off the top of their heads. Don't feel bad. Problems
> crop up all the time for an admin, that's why they pay you
> the (not so <g>) big bucks!
> 
Heh. I actually only took the job back when the offer came with a 
significant raise over my previous salary.

[...]

 >> I've verified that it isn't a case of someone
 >> else using the file - there are no users on the system except myself, as
 >> root, checking the issue (not running any filepro apps), and the single
 >> user experiencing the problem which I had logged in to troubleshoot. I
 >> verified that there were no stale logins, `ps aux` revealed only the
 >> expected user's single session.


 >What, exactly, is "the problem"?

The problem was a user being locked out of files when no one else was 
using the system, and no processes were running in the background that 
touched filepro.

 > Define "empty".  And, if you're looking at something called ".lockfile"
 > as you keep typing, you're looking at something that's not filePro, as
 > that would be "lockfile".

Doh. You are right, of course. And I was looking at 'lockfile' ... an 
error in translation when composing my message. My bad.


Once again, thanks for all of the input, everyone. One of the things I 
missed about working with this employer, and indeed working with 
filepro, was this list. You've yet again shown that despite being a 
diverse group, you are knowledgable about your subject matter, and 
willing to help those who don't quite 'get it'.

Although the problem turned out to be not something specifically related 
to filepro - i.e. it was a network connectivity issue that was causing 
improper exiting fromt the filepro system, and filepro was, quite 
properly, not releasing files when the user working with them was 
disconnected, I am in your debt, and you have my gratitude.

Thanks,

Silas Martinez