<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think I know what is going on now probably because I went through
this myself. <br>
<br>
If you are using Linux as your file server then you can't use the
original Netware tools (Monitor) to find out which files are being
locked and that seems to be what you are looking for.<br>
<br>
If your Linux box is using Samba for serving the Windows file then you
want to look at installing/running SWAT. (Samba Windows Administration
Tools) This has a nice little "status" view that will let you see what
files all users have open. To see it by user, or "client", as SWAT
calls them, then scroll down to the bottom of that page and click the
"Show Client in co 1" button.<br>
<br>
Showlock will not work for FP running on Windows clients off a Linux
file server.<br>
<br>
<br>
Boaz<br>
<br>
<blockquote type="cite">
<pre wrap="">Message: 5
Date: Thu, 21 Aug 2008 10:17:07 -0400
From: "Nathan Lehman" <a class="moz-txt-link-rfc2396E"
href="mailto:nlehman06@gmail.com"><nlehman06@gmail.com></a>
Subject: Re: Help converting to a new Linux server
To: <a class="moz-txt-link-abbreviated" href="mailto:john@valar.com">john@valar.com</a>
Cc: <a class="moz-txt-link-abbreviated"
href="mailto:filepro-list@lists.celestial.com">filepro-list@lists.celestial.com</a>
Message-ID:
<a class="moz-txt-link-rfc2396E"
href="mailto:a98df1d00808210717y75d76a6eh6f659e1ffb37c919@mail.gmail.com"><a98df1d00808210717y75d76a6eh6f659e1ffb37c919@mail.gmail.com></a>
Content-Type: text/plain; charset=ISO-8859-1
Thanks for the awesome advice. That is exactly what I was looking to
get back. However, I'm a newbie to Linux stuff so, at the expense of
me sounding really dumb, I have a couple more questions on the
solutions that you provided me.
I am having trouble finding how to run showlock, lock.info, and
setperms. Does it matter that I'm running the Windows version of
filePro and not the Linux? All of the clients that access filePro
here are running Windows. The server where filePro is stored is
Linux. Can I still use showlock, lock.info, and setperms on this? If
so, is there some documentation on how to run these scripts. Like I
said, I'm a newbie to Linux.
Thanks for your patience and advice.
Nathan Lehman
On Wed, Aug 20, 2008 at 11:48 PM, John Esak <a
class="moz-txt-link-rfc2396E" href="mailto:john@valar.com"><john@valar.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> </span>If you really want to solve your record locking problem ... whose locking a
<span class="moz-txt-citetags">> </span>record when it should be available... You need to look at all of your
<span class="moz-txt-citetags">> </span>processing. Here is where the problem lies. All your trouble is being
<span class="moz-txt-citetags">> </span>generated there. FilePro does not cause record locking conflicts... in
<span class="moz-txt-citetags">> </span>fact, it has never, not once, in the nearly 30 years I've used it, ever been
<span class="moz-txt-citetags">> </span>the <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>cause<span class="moz-txt-tag">*</span></b> of a record locking issue. It has been fully vetted over and
<span class="moz-txt-citetags">> </span>over again in this regard... and without fail, the reason for a record being
<span class="moz-txt-citetags">> </span>locked when it shouldn't be... is the, is the sole province of the
<span class="moz-txt-citetags">> </span>programmer and the processing tables being used.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>Sorry to take the long view... but somebody has to... get a hold of some old
<span class="moz-txt-citetags">> </span>Guru magazines, Smalltalk's , fPDJ's and so on... there are myriads of
<span class="moz-txt-citetags">> </span>examples of how to build your tables so no conflicts will occur.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>One of the main culprits I think, is working from within @key's routines.
<span class="moz-txt-citetags">> </span>This unnecessarily <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>locks<span
class="moz-txt-tag">*</span></b> the record, so other reports, or clerk accesses
<span class="moz-txt-citetags">> </span>get stopped dead in the water. I have yet to find an @key routine that can
<span class="moz-txt-citetags">> </span>not be transformed into an @entsel version, even including changing values
<span class="moz-txt-citetags">> </span>of the real fields on the current record. It just takes little re-writes
<span class="moz-txt-citetags">> </span>here and there to open up your files to virtually complete access without
<span class="moz-txt-citetags">> </span>the fear of records being locked when they shouldn't be. If you do lock a
<span class="moz-txt-citetags">> </span>record, do it for the shortest time you possibly can, and do it and lock and
<span class="moz-txt-citetags">> </span>unlock it correctly so you keep indexes correct as well.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>As to your actual question, the sholock program Ken mentioned is the tool
<span class="moz-txt-citetags">> </span>you want, but he is also correct it is 100% more effective if you use it
<span class="moz-txt-citetags">> </span>within Bob Stockler's lock.info script.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>Secondly, his mention of checking your lookups with CHECKLOCK is the very
<span class="moz-txt-citetags">> </span>best way to <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>quickly<span
class="moz-txt-tag">*</span></b> find improper code.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>Third, you can do something to all subdirectories and files with wildcards
<span class="moz-txt-citetags">> </span>much easier in Linux than in any Windows platform. Roughly it might look
<span class="moz-txt-citetags">> </span>something like this.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>Cd /appl/filepro #(where your files live)
<span class="moz-txt-citetags">> </span>chmod 700 * */* #Change ownership of all filePro files and dirs
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>But, again, Ken's suggestion to run setperm in the fp/scripts directory is
<span class="moz-txt-citetags">> </span>really all you need.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>Cd /appl/fp/scripts #or wherever your programs are
<span class="moz-txt-citetags">> </span>./setperms
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>This must be done as the root user.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>Good luck, The hard to understand part of all this is why you didn't have
<span class="moz-txt-citetags">> </span>the problems under Netware.... perhaps, it does not lock files as
<span class="moz-txt-citetags">> </span>thoroughly (i.e., strictly... in <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>alls<span
class="moz-txt-tag">*</span></b> circumstances) as it should. I've
<span class="moz-txt-citetags">> </span>never been a fan of Netware, maybe It's okay, but I have no experience with
<span class="moz-txt-citetags">> </span>it. I only have had run-ins with all the other products that Novel has
<span class="moz-txt-citetags">> </span>ruined over the years.... WordPerfect, Corel, Unix... etc. <span
class="moz-smiley-s1"><span> :-) </span></span> Whatever
<span class="moz-txt-citetags">> </span>the reason, now that you are on Linux, you have to deal with its full record
<span class="moz-txt-citetags">> </span>locking paradigm... and if you write your code properly, it will be no
<span class="moz-txt-citetags">> </span>burden.
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>John Esak
<span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">></span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> </span>-----Original Message-----
<span class="moz-txt-citetags">>> </span>From: <a
class="moz-txt-link-abbreviated"
href="mailto:filepro-list-bounces+john=valar.com@lists.celestial.com">filepro-list-bounces+john=valar.com@lists.celestial.com</a>
<span class="moz-txt-citetags">>> </span>[<a
class="moz-txt-link-freetext" href="mailto:filepro-list-bounces+jo">mailto:filepro-list-bounces+jo</a> <a
class="moz-txt-link-abbreviated"
href="mailto:hn=valar.com@lists.celestial.com">hn=valar.com@lists.celestial.com</a>] On
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">> </span>Behalf
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> </span>Of Kenneth Brody
<span class="moz-txt-citetags">>> </span>Sent: Wednesday, August 20, 2008 11:14 PM
<span class="moz-txt-citetags">>> </span>To: Nathan Lehman
<span class="moz-txt-citetags">>> </span>Cc: <a
class="moz-txt-link-abbreviated"
href="mailto:filepro-list@lists.celestial.com">filepro-list@lists.celestial.com</a>
<span class="moz-txt-citetags">>> </span>Subject: Re: Help converting to a new Linux server
<span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>Quoting Nathan Lehman (Wed, 20 Aug 2008 22:12:41 -0400):
<span class="moz-txt-citetags">>></span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> > </span>filePro 5.0.14D9
<span class="moz-txt-citetags">>> > </span>Novell Open Enterprise Server 2 on Suse Linux Enterprise Server 10
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>[... moved from Netware to Linux ...]
<span class="moz-txt-citetags">>></span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> > </span>One of the issues we are having with this new server is dealing with
<span class="moz-txt-citetags">>> > </span>file locks. I find it really hard to find out who is locking a key
<span class="moz-txt-citetags">>> > </span>file. The way we do it now is to run ncpcon from the server. However
<span class="moz-txt-citetags">>> > </span>this just shows everyone accessing the key file, not the one(s)
<span class="moz-txt-citetags">>> > </span>locking it.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>Get a copy of my showlock program, perhaps with Bob Stockler's lock.info
<span class="moz-txt-citetags">>> </span>wrapper.
<span class="moz-txt-citetags">>></span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> > </span>I found after the first day that we needed to set all filePro files
<span class="moz-txt-citetags">>> > </span>with the -sh (shareable) attribute. That really helped.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>Why? What problems were you having, and how did it help? I'm not
<span class="moz-txt-citetags">>> </span>familiar with a "shareable" attribute under Linux. How, exactly, did
<span class="moz-txt-citetags">>> </span>you set this?
<span class="moz-txt-citetags">>></span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> > </span>However I'm
<span class="moz-txt-citetags">>> > </span>not good enough at linux to know how to change all files in my filePro
<span class="moz-txt-citetags">>> > </span>and fp folders and have it change the attributes in every file
<span class="moz-txt-citetags">>> > </span>including the files in subfolders. Right now I have to go into each
<span class="moz-txt-citetags">>> > </span>folder and change all the files in that folder, then move to the next
<span class="moz-txt-citetags">>> > </span>folder and do the same thing.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>Use the setperms script that filePro includes. That's all that you
<span class="moz-txt-citetags">>> </span>should have to do.
<span class="moz-txt-citetags">>></span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> > </span>One other problem that seems to be occurring more often on this server
<span class="moz-txt-citetags">>> > </span>is freechain rebuilds. I'm not quite sure why this is happening more
<span class="moz-txt-citetags">>> > </span>often.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>Add PFCHECKLOCK=ON to the filePro config file and see if you have any
<span class="moz-txt-citetags">>> </span>unprotected lookups being modified. (Note, however, that this would
<span class="moz-txt-citetags">>> </span>have caused problems in Netware as well, if you had more than one
<span class="moz-txt-citetags">>> </span>person in at a time.)
<span class="moz-txt-citetags">>></span>
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">>> > </span>I guess I would just like to know if anyone has any tips or tweaks in
<span class="moz-txt-citetags">>> > </span>general for running filePro from my new linux server and if anyone has
<span class="moz-txt-citetags">>> > </span>any suggestions for the problems listed. Thanks so much in advance.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>--
<span class="moz-txt-citetags">>> </span>Read the truth behind the movie "Expelled" at
<span class="moz-txt-citetags">>> </span><a
class="moz-txt-link-rfc2396E" href="http://www.ExpelledExposed.com"><http://www.ExpelledExposed.com></a>
<span class="moz-txt-citetags">>> </span>--
<span class="moz-txt-citetags">>> </span>KenBrody at BestWeb dot net spamtrap: <a
class="moz-txt-link-rfc2396E" href="mailto:g8ymh8uf001@sneakemail.com"><g8ymh8uf001@sneakemail.com></a>
<span class="moz-txt-citetags">>> </span><a
class="moz-txt-link-freetext" href="http://www.hvcomputer.com">http://www.hvcomputer.com</a>
<span class="moz-txt-citetags">>> </span><a
class="moz-txt-link-freetext" href="http://www.fileProPlus.com">http://www.fileProPlus.com</a>
<span class="moz-txt-citetags">>> </span>_______________________________________________
<span class="moz-txt-citetags">>> </span>Filepro-list mailing list
<span class="moz-txt-citetags">>> </span><a
class="moz-txt-link-abbreviated"
href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<span class="moz-txt-citetags">>> </span><a
class="moz-txt-link-freetext"
href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>_______________________________________________
<span class="moz-txt-citetags">> </span>Filepro-list mailing list
<span class="moz-txt-citetags">> </span><a
class="moz-txt-link-abbreviated"
href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<span class="moz-txt-citetags">> </span><a
class="moz-txt-link-freetext"
href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
<span class="moz-txt-citetags">></span>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>