|Subject:||Re: Is it possible to run lout without it writing to the file system?|
|Date:||Sun, 11 Sep 2011 13:36:38 +0100|
|User-agent:||Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:188.8.131.52) Gecko/20110505 Icedove/3.0.11|
I don't know the answer to your question but I do know a workaround. The special files, which lout needs when doing multiple passes, are created in the current directory, hence conflicts can be avoided by ensuring that each instance of lout runs in its own working directory. You can create a temporary directory for this purpose and delete it when finished. I use lout in this way to generate typeset documents in a web application. The web application creates a temporary directory with a unique name (based on the session id), runs lout in that directory then deletes the directory. The PHP code is something like
$cmd = "cd $tempdir ; lout -r 3 -PDF $tempfile ; rm * ";
$pdf_document = sys_exec($cmd);
where $tempdir is the path of the temporary directory, $lout_document is the input to lout and $pdf_document is the PDF output.
If security is a particular concern then you could create an encrypted file system on the fly to hold the temporary directory and delete the encrypted file system when finished, for example.
On 11/09/11 01:52, Daniel Kauffman wrote:
Is it possible to run lout without it writing to the file system?
|[Prev in Thread]||Current Thread||[Next in Thread]|