Odd Global .lockfile problem

[Kenneth Brody]

Quoting Silas Martinez (Tue, 14 Jun 2005 15:42:35 -0700):
[...]
> Thanks for the input, Laura. Here is the thing - users are getting
> locked out of files that have an empty .lockfile in them.

If you are getting "someone else is using this file", then the lockfile
cannot be empty.

What is the exact error you are getting?

[...]
> 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"?

[...]
> I've disabled the cron job again, and will check the contents of any and
> all lockfiles again - but I'll note that I had checked this before, and
> indeed .lockfile for the file the user was unsuccessfully trying to
> access was empty.

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".

[...]
--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com