Thursday, March 28, 2024 1:54:26 PM

Secure Lockdown seems to stop the writing of a log file

11 years ago
#431 Quote
I have an interactive setup running custom software and the log file that is being open, written to, and closed, is not getting written while Secure Lockdown is running.  Is there any reason for this?  If so, is there a work around that you can suggest?  Thanks in advance.
0
11 years ago
#432 Quote
Where (what path) and how is the log file being written?
0
11 years ago
#438 Quote
The path is directly under C:\ in a folder synced with Dropbox.
0
11 years ago
#439 Quote
and the writing is all done with file open and close.

FILE *tmp = fopen("heartbeat.txt","w");
fprintf(tmp, boost::posix_time::to_simple_string(now).c_str());
fclose(tmp);
0
11 years ago
#440 Quote
What version of Secure Lockdown are you using? Is this script running froma a browser?
0
11 years ago
#442 Quote
Secure Lockdown v.2
The application a local C++ application. run through a batch script calling the executable.  Not browser based.
0
11 years ago
#443 Quote
Are you using the Working Directory feature in Secure Lockdown? Sometimes programs require this to work properly. There is not anything in particular that Secure Lockdown does to prevent writing to a specific folder location if a program wants to do that.

Also, if you're running a script to launch an application, Secure Lockdown may not be able to monitor the running app because it was launched from a script. It wont know what to monitor (for example to Keep it Running if it is closed)
0