Changing gears a little bit I found a workaround… using my mounting script I added the commands that handle the file copying. That eliminates the need for a CRON task to handle disk reformatting and ejection. Not ideal but it will work for now. > On Jun 14, 2018, at 11:38 AM, Ryan Coleman <RYAN.COLEMAN at CWIS.BIZ> wrote: > > > >> On Jun 14, 2018, at 11:04 AM, Iznogoud <iznogoud at nobelware.com <mailto:iznogoud at nobelware.com>> wrote: >> >> Absolutely no guarantees on data integrity... Modifying the filesystem can take >> an arbitrary amount of time, at which time the user can yank out the USB, which >> is something they can do at anytime, etc, etc. > > If my photographer fails to follow the instructions… they don’t get paid. it’s in the contract. :) > >> >> Maybe we need to think "out of the box" here, as I was discussing with a friend >> about this offline. Do it like ATMs, where they take your card, do what there >> is to do, and return it in the end. Have the USB behind a "hatch" that opens >> when the drive is to be attached. Then close it... You get the idea. You open >> the hatch to let the user unplug it after you have successfully unmounted. For >> safety, you can introduce a forced ejection by the user, should they think that >> the process is taking too long, but after they have been warned of the potential >> issues. > > Again, I’m not concerned about that - it’s designed to insert the cards and walk away. :) > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20180614/16ffed7d/attachment.html>