Re: error if texmf.fndb and mpm.fndb are not writable, even if no write is occuring

> Imho this sort of installation doesn't make sense.

What I described is not actually what we're doing. I was trying to give a simpler situation.

Here is  the complete story:

We include the portable version of MikTeX in our software distribution 
because we have a report generation tool that uses MikTeX as a back end. 
Our users don't actually use MikTeX directly. The report generation tool 
is command line only. The MikTeX executables that we use are accessed by 
our report generation tool and are used in "batchmode". (BTW, we include 
copyright notices, etc., for MikTeX in the distribution.)

What we did is this.

1) we downloaded the portable version of MikTeX and installed it.

2) we ran the portable version on a tex file that downloads all the 
packages to which our users need access for the report generation tool.

3) we then include the MikTeX directory in our distribution. Our report 
generation tool (python) executes the MikTeX executables it needs to. 
Because we're using the portable version, no MikTeX initialization or 
Windows registry access is needed.

This actually works except for one small feature: MikTeX's pdflatex and 
latex need the files texmf.fndb and mpm.fndb (in miktex/data/le)  to be 
writeable by users, specifically, users with non-admin accounts. If we 
make these two files writeable, this approach works without any problems.

(If they aren't writeable, errors like "pdflatex: Windows API error 5: 
Access is denied" occur.)

The issue with this approach is that our customers are typically 
installing our software, including the MikTeX directory, in Program 
Files.  Some of our customers have a security requirement that no file 
in Program Files can be writeable by users. Also, these are often 
multiuser environments.

It does seem from the tests I ran that texmf.fndb and mpm.fndb do not 
need to be writeable if all the packages needed are already installed. 
Specifically, if all the packages are already available, pdflatex and 
latex do not change the contents or the time stamps of texmf.fndb and 
mpm.fndb.

I see that my real question is: is there some way to configure the 
portable version MikTeX so that write access to texmf.fndb and mpm.fndb 
is not needed.

On 04/24/2013 12:19 AM, Ulrike Fischer wrote:
> Am Tue, 23 Apr 2013 15:20:45 -0700 schrieb Rick Pember:
>
>>   > I think you should give more informations
>>   > regarding the accounts and > the installation.
>>
>> Here's what I did in detail:
>>
>> 1) create restricted user account "user1" and log in to that account.
>> (restricted = non-administrator)
>>
>> 2) download MikTeX Portable 2.9.4757 to desktop
>> -- we're using the portable package because we want to create a portable
>> folder containing MikTeXwhich we can then give to our customers and
>> which they can then use in a restricted account
>>
>> 3) create a folder MikTeX and move installer into it
>>
>> 4) open folder MikTeX and double click extractor.
>> -- extract to C:\Documents and Settings\user1\Desktop\MikTeX
>> --twoofthefilestheextractorinstallsare
> ....
>> 9) Now right click texmf.fndb and mpm.fndb again and click "Deny" on
>> Write access for user1.
>>
>> Recall this is what our customer is requiring for an installation in
>> Program Files.
> Imho this sort of installation doesn't make sense. You are trying to
> move a portable installation - meant for users which can't write to
> program files - to this very place. Naturally the portable MikTeX
> assumes that it has full writing access to its data - what do you
> expected? The main point of a portable application is that it
> doesn't use user profiles but its main folder.
>
> In my opinion your user1 has these options:
>
> 1. He installs a normal MikTeX in his restricted account in some
> folder outside program files where he has writing rights. This will
> give him a single user installation for this account. This works
> without any problems - I have such installations on various PC
> including one where I have very restricted rights.
>
> This won't need writing rights for program files at all - neither
> during installation nor when using MikTeX.
>
> 2. If he has writing rights during the installation:
>
> - He could also try to make a single user installation in program
> files. It *could* work and need writing rights only if new packages
> need to be installed afterwards. But I never tried this.
>
> - Or he installs a multiuser installation. User1 can that use this
> MikTeX in his account without writing rights for program files. New
> packages will be installed to his user profile.
>
>


-- 
Richard Pember, Ph.D.
Director of CFD Development
Altair Engineering, Inc.
2685 Marine Way, Suite 1421
Mountain View, CA 94043
(650) 988-9700 x715 (Office)
(650) 988-9770 (Fax)
[email protected]
http://www.altair.com


------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr