Jump to content


  • Content Count

  • Joined

  • Last visited

About mandrews58

  • Rank
  1. Apologies for not being clearer on this: if you don't care about keeping the log file at all, there is no need to setup a RAM drive. Simply use junction to point from the default splogs folder to any non-existent folder, and the log file never gets written - problem solved. If you ever decide you need the log file for some reason, it's probably easiest to just delete the junction, recreate the actual splogs folder, and let stpass write to it. When done with the logging, delete splogs folder and recreate the junction pointing to nowhere
  2. I use a 1GB ramdisk, but that amount of RAM is not required for stpass - the ramdisk is used for browser temp folders and so on. For stpass - i actually pointed junction at a folder on the ramdisk named 'splogs' but i didn't actually create the folder. stpass keeps running without issue, so presumably it does a check for the existence of the folder, and simply skips writing to the log file if the splogs folder does not exist. That's nice - no overflow concerns, no superfluous logging. If i ever needed the log, i would simply create the folder splog on the fly - no need to stop stpass - and stpass.exe starts writing to the spLog.log file from that point on. If you want to keep the spLog.log around all the time, overflow becomes an issue. I haven't done this, but you could create a shell script to 1) stop the stpass service, 2) delete the splogs.log file and 3) restart stpass. Run this batch file periodically using task scheduler in windows - Control Panel\All Control Panel Items\Administrative Tools\Task Scheduler. The task scheduler wizard will run you through the setup; be sure to specify the Action->settings->start in folder or the task might not run (this isn't obvious and trips some people up)
  3. I had this issue with pure 3.0 stpass hammering the hard drive. Here is how you can get around it - if it's worth the hassle to you: 1) install a RAM drive - go to http://memory.dataram.com/products-and-ser...oftware/ramdisk and install the lite version. 2) go to sysinternals and download junction http://technet.microsoft.com/en-us/sysinternals/bb896768 junction is used to create a symbolic link from the splogs directory to your ramdrive. In other words you erase the actual splogs directory and replace it with a filesystem symbolic link to the root directory on your ram disk. Stpass will continue to hit the splogs file, but now it's in RAM. HTH
  4. I'm running PURE 3 on a windows 7 x64 box and have the following question about integrated password manager stpass.exe writes a file spLog.log in appdata\temp\splogs once a second. I'd like to turn off this logging - there's nothing interesting in the log and it really pounds the hard drive, as in a noticeable thumping sound. Help indicates the Support Tools window should have a feature to manage logging, but no it's not there. To get around this problem temporarily, I used sysinternals junction to make a symbolic link to the password manager's splogs directory on a RAM disk - no more thumping, but it's not a real solution. So: how do I control logging in password manager? I'm fine to mess with the registry if necessary. Thanks in advance.
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.