Re: [time-nuts] Dropbox is cool, but...
On Mon, Feb 6, 2017 at 1:19 AM, Bruce Lane wrote: > > > On 05-Feb-17 16:42, Didier Juges wrote: > >> Yes, I noticed that before. >> I have a number of tools that don't like running off a Dropbox folder, >> including several software development tools for starter. Too many files >> opened at the same time. >> Don't assume that because it looks like a normal folder, it works like one, >> even though for many things, it does work remarkably well. > > > > In the interest of presenting alternatives -- I dumped Dropbox a while > back, due to their increasingly invasive 'privacy' policies. > > A good alternative for me has been Sync: https://www.sync.com/ > > Their 'Free' package includes 5GB -- More than I would ever possibly > use for an online sharing account. ;-) > > Keep the peace(es). > For private sync between machines (on the local LAN and over the Internet) I use https://syncthing.net/ ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Dropbox is cool, but...
I've had similar results with LTSpice, by default it tosses the simulations results to the current working directory. Fortunately, you can tell LTSpice to use a specific temp folder for simulation results. On Sun, Feb 5, 2017 at 7:42 PM, Didier Juges wrote: > Yes, I noticed that before. > I have a number of tools that don't like running off a Dropbox folder, > including several software development tools for starter. Too many files > opened at the same time. > Don't assume that because it looks like a normal folder, it works like one, > even though for many things, it does work remarkably well. > > On Feb 5, 2017 2:32 PM, "John Ackermann N8UR" wrote: > > > So I was clever and decided to log some PPS data to a folder within my > > "Dropbox" folder. Strange results followed... the whole system just > bogged > > down, and even fairly slow serial data dropped characters. > > > > It turns out that the culprit was the Dropbox daemon continuously trying > > to sync the file as it changed every second. It didn't manifest as CPU > > overload or anything obvious; the problem was apparently thrashing in the > > I/O system. Once I started dumping the data to a "normal" directory, the > > problem went away. (This was on Linux, by the way). > > > > So, a lesson learned -- don't stream unbuffered data, even at a low rate, > > into a sync'd folder! > > > > John > > ___ > > time-nuts mailing list -- time-nuts@febo.com > > To unsubscribe, go to https://www.febo.com/cgi-bin/m > > ailman/listinfo/time-nuts > > and follow the instructions there. > > > ___ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/ > mailman/listinfo/time-nuts > and follow the instructions there. > ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Dropbox is cool, but...
On 05-Feb-17 16:42, Didier Juges wrote: > Yes, I noticed that before. > I have a number of tools that don't like running off a Dropbox folder, > including several software development tools for starter. Too many files > opened at the same time. > Don't assume that because it looks like a normal folder, it works like one, > even though for many things, it does work remarkably well. In the interest of presenting alternatives -- I dumped Dropbox a while back, due to their increasingly invasive 'privacy' policies. A good alternative for me has been Sync: https://www.sync.com/ Their 'Free' package includes 5GB -- More than I would ever possibly use for an online sharing account. ;-) Keep the peace(es). -- --- Bruce Lane, ARS KC7GR http://www.bluefeathertech.com kyrrin (at) bluefeathertech dot com "Quando Omni Flunkus Moritati" (Red Green) ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Dropbox is cool, but...
Yes, I noticed that before. I have a number of tools that don't like running off a Dropbox folder, including several software development tools for starter. Too many files opened at the same time. Don't assume that because it looks like a normal folder, it works like one, even though for many things, it does work remarkably well. On Feb 5, 2017 2:32 PM, "John Ackermann N8UR" wrote: > So I was clever and decided to log some PPS data to a folder within my > "Dropbox" folder. Strange results followed... the whole system just bogged > down, and even fairly slow serial data dropped characters. > > It turns out that the culprit was the Dropbox daemon continuously trying > to sync the file as it changed every second. It didn't manifest as CPU > overload or anything obvious; the problem was apparently thrashing in the > I/O system. Once I started dumping the data to a "normal" directory, the > problem went away. (This was on Linux, by the way). > > So, a lesson learned -- don't stream unbuffered data, even at a low rate, > into a sync'd folder! > > John > ___ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/m > ailman/listinfo/time-nuts > and follow the instructions there. > ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Dropbox is cool, but...
Yep, I can see where that would be an issue Use an un-synced directory/folder and them back up to dropbox off-air if required... :) __ Clay Autery, KY5G MONTAC Enterprises (318) 518-1389 On 2/5/2017 2:17 PM, John Ackermann N8UR wrote: > So I was clever and decided to log some PPS data to a folder within my > "Dropbox" folder. Strange results followed... the whole system just > bogged down, and even fairly slow serial data dropped characters. > > It turns out that the culprit was the Dropbox daemon continuously > trying to sync the file as it changed every second. It didn't > manifest as CPU overload or anything obvious; the problem was > apparently thrashing in the I/O system. Once I started dumping the > data to a "normal" directory, the problem went away. (This was on > Linux, by the way). > > So, a lesson learned -- don't stream unbuffered data, even at a low > rate, into a sync'd folder! > > John ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
