I’m trying to use Yarra to backup TWIX data from multiple (12 total) scanners onto a single network drive (it’s a windows-based shared drive). Early on we ran into an issue where yarra’s “queue” folder was filling up and slowing down our scanners. Eventually, I realized that the shared drive will only allow us to connect from one scanner at a time (we are using the same login from each scanner), so once one scanner connected, all the others would not be able to connect, so the queue would grow and grow until the scanner slowed down. I could create individual users for each scanner, but that’s a pain to maintain yearly password changes for 12 scanners. Instead, I've learned windows will allow me to connect to the same shared network drive with the same user name so long as I don’t connect by ip address – instead I connect by a unique hostname from each scanner. So far this has solved the problem, but I’d like to take it a step further and try to minimize the amount of time each scanner is connected to the network drive. Is there a way to disconnect the network drive after backup?
Also, can someone explain the difference between putting "net use" networking commands into the "connect cmd" field on the "networking tab" vs in the "startup commands" tab?
Hi @tblock79 and others,
we're now having problems with RDS when we record large data files (>100GB). Unfortunately the C:-drive with the queue directory does not have a lot of free space, so those files >100GB cannot be exported via the queue.
What is your strategy to handle large files?
I've been thinking about a direct export feature, as discussed a couple of years ago. Basically having a parameter in rds.ini that would skip the queue and directly write the files to the network drive.
What do you think? Would you be willing to implement this? Or would you accept a patch into the official codebase?
@fyrdahl Hi Alexander, Yes, you can sign the Yarra client with your own (IDEA) developer certificate using the signtool.exe. I am just using the following .bat batch file for that, but a Python script would do it as well:
signtool.exe sign /fd SHA256 /f [put path & name of the certificate here].pfx %1%
You need to make sure to sign all .exe files, as well as all the .dll files (including the ones in the subfolders, such as \platforms)
Sign in to start chatting.