leveraging PFDSK

[Bob Stockler]

On Thu, Sep 09, 2004 at 08:08:34AM -0500, Jeremy Anderson wrote:
| John Esak wrote:
| 
| >
| >No, it is accomplished through a more internal search mechanism which uses
| >the mount table and similar basic paths. Note your first two paths on the
| >working machine and how they are different from the ones you want to use.
| >They are:
| >
| >  /appl/....
| >  /appl2/....
| >
| >By changing to the way you have it you lose the mechnism filePro is 
| >actually
| >using which is to search the mount table, and run any filePro files found 
| >in
| >absolutely similar paths starting *after* the original mount name... in 
| >your
| >case /appl and /appl2 both have filepro/filename/... after them and that is
| >why they are found.
| >
| >>In my script, I have tried setting PFDSK to be "/appl/test:/appl/test2",
| >>but this does not work in the way which I expected.
| >>Is what I'm trying to do possible?
| >>If so, what is the best way to go about what I'm trying to do?
| >
| >The PFDSK variable really means what it says... DSK or DISK... or volume...
| >or mounted filesytem... like D:, E:, F: and /appl, /u/appl, /hd2, etc.
| > 
| /appl is not, however, a separate mount point from /
| My reasoning was that under Unix, a directory and a mountpoint are not 
| inherently different from an application point-of-view.  I suspect this 
| is a case, however, where it is.

Back when we were using 15 Mb hard disks on Xenix it usually
was a mount point.  Now, however, on my 33 Gb single hard
disk I have PFDSK set to "/u:/u3", and $PFDATA$PFDIR is set
to "/u/appl".  filePro finds my filePro files and their map
files, programs, screens, etc. in "/u/appl/filepro" and some
of those files' key files and indexes in "/u3/appl/filepro",
though they're all on the same hard disk.

| >I'm not sure what you want to do is possible. I think not. Maybe others can
| >find a way...
| > 
| >
| I thinkI can use symbolic links between the two...  Is this safe?  Can I 
| dare just link the key into the directory with all the other stuff?  Or 
| will filepro barf?  It appears to work when I test it on my Linux box, 
| but I'm worried about unseen and delayed side-effects.
| 
| >	I think you can still do this sort of thing without having to split 
| >	up
| >everything so much. Is this a very crowded (not much disk space)system??
| >
| It was.  I'm moving it to a new server, though, where disk space will be 
| available a-plenty.  Until then, however, I need to make it work on the 
| aged MP-RAS box, where space is precious.
| 
| On another subject, Ken asked about the values of PFDATA and PFDIR. 
| This is what my script returns:
| 
| PFDATA is
| PFDIR is /appl/test
| PFDSK is /appl/test:/appl/test2

You've got it bassackwards.  Move your directories around
so that you have something like:

      /test/appl/filepro
and:
      /test2/appl/filepro

Then:

  PFDATA=/test
  PFDIR=/appl
  PFDSK=/test:/test2

Your filePro files and the maps, screens and programs would go
in /test/appl/filepro.  Your data files and indexes could then
be in either /test/appl/filepro or /test2/appl/filepro/

Bob

-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).