PSPP-BUG: Re: [bug #23344] Use /tmp for temporary files

[unknown-1]

Hi

Indeed these files are the problem. If they can't be created, at least in Windows, you wan't have an output screen. You wan't see anything at the moment you ask for frequencies etc. It is correct that PSPPire doesn't crash on it, but it also doesn't work like intended.

The problem for me is:
- I need write access on the current directory so PSPPire can write the output files you mentioned
- in the current situation PSPPire leaves files behind in directories. In my opinion this is not a clean behavier. 
- if installed in a standard windows way, a standard user won't have write access on the current directory and also not on /usr....
- a clever system administrator won't give his users write access to a directory in the software path 
- PSPPireWidget seems only to work if it is available in the current directory 

The work around I use:
- switch to the /tmp directory
- copy the PSPPireWidget to this directory 
- start PSPPire

This is not a clean solution because:
- in a .bat I can't easily switch to the drive where /tmp is located. If /tmp is on another drive as the installation drive, it is necessary to change the psppire-start2.bat manualy , or PSPPire won't start. 
- I create an additional overhead by copying the widget dll.
- The system is a little bit opener for an attack because an attack can target this widget dll

Background:
- To avoid having strange privilege configurations I mount (runtime) /tmp on the windows temp directory like defined in the environment variables. 
- To make things a bit easier for users, I mount /home on the windows userprofile so users can find there Desktop files etc.

All this may seem to be a little theoretic, but I guess this will cause problems on networks. Especially when strict security is enforced. You can read this as, this will cause problems on schools, universities etc.

Hope this helps
CU