If the files are _required_ to remain until the next time the user
runs
OOoLilypond, /tmp might not be the best place. On some unices, /
tmp is
a swap-based filesystem that gets trashed at reboot; on others
(including various Linux distros), there's a cron job that removes
anything that has not been accessed for some period of time.
On Fri, 2006-10-13 at 09:15 +0200, Mats Bengtsson wrote:
Samuel Hartmann wrote:
Hi Mats,
Mats Bengtsson wrote:
Samuel Hartmann wrote:
* on Linux, ~/.ooolilypond-tmp is used for temporary files
Why not use a directory in /tmp/ for temporary files? I'm probably
not the
only one who has $HOME on a network file system with limited quota.
Of course, I could add a soft link from .ooolilypond-tmp to /tmp/.
Using /tmp can cause problems when several users use OOoLilyPond on
the same machine. The temporary files are the LilyPond input
file, the
LilyPond output, the eps or png file. These file stay in the
temporary
directory until the next time you run OOoLilyPond. Another user
running OOoLilyPond will have problem deleting or overwriting these
files.
Such problems are easily handled by creating separate subdirectories
below /tmp/,
for example based on the user name or using tmpfile().
/Mats
_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user