You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The memory dump file is output to the current working directory even when a full or relative path is specified with the --output-dir argument. This is not the case with the --log-dir argument, which does output the log file to the specified path.
I'm using Margarita Shotgun v0.4.0 on an Ubuntu Server 16.04 EC2 instance, which is configured as a SIFT v3 workstation.
The following is a sample run, where the directory output_dir already exists in the current working directory. I also tried outputting the memory dump file to a different output directory than the log file, but got the same results.
The memory dump file is output to the current working directory even when a full or relative path is specified with the --output-dir argument. This is not the case with the --log-dir argument, which does output the log file to the specified path.
I'm using Margarita Shotgun v0.4.0 on an Ubuntu Server 16.04 EC2 instance, which is configured as a SIFT v3 workstation.
The following is a sample run, where the directory
output_dir
already exists in the current working directory. I also tried outputting the memory dump file to a different output directory than the log file, but got the same results.The text was updated successfully, but these errors were encountered: