logtext and logfile

[Brian K. White]

Not having tested, and since 
http://www.fptech.com/Products/Docs/fpmanhtm/references/version_reference/environment_variables_1.htm
(arrived at by googling "filepro environment variables")
does not specify, then the logical places to look are:

1) current directory where user is sitting when clerk/report starts
2) PFTMP
3) fpmerge
4) /tmp

Though you're right, it would be nice for any "could not open" error message 
to say what it couldn't open.

Then again I would never use a relative path or simple filename devoid of 
path without knowing where it was going to go in the first place.
logfile="smith" ?? what were you thinking?

In case it's #1, maybe the problem is clerk/report, which are suid filepro, 
does not have permission to create files in user foo's home directory?

-- 
Brian K. White    brian at aljex.com    http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!


----- Original Message ----- 
From: "Robert Pulliam" <pulliamr at earthlink.net>
To: <filepro-list at lists.celestial.com>
Sent: Sunday, March 02, 2008 4:33 PM
Subject: logtext and logfile


Using dos in configuration editor   logfile   value smith
                                                 pflogappend   value on

Same in unix

Processing
        qw = @rn{","{1
        logtext = qm        the same in both

It works in dos but not in unix

in unix the same processing gives me a popup error in the fileprogram "open 
of logfilefailed, error 13"

Question 1.  What is wrong
               2.  Where would the file be placed in unix if it were opened?

thanks   Robert Pulliam MD


--------------------------------------------------------------------------------


> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>


--------------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.21.2/1304 - Release Date: 2/29/2008 
8:18 AM