Re: [fossil-users] Is it advisable to put a .fossil repository on Dropbox?
On Fri, May 9, 2014 at 3:25 AM, Gerald Gutierrez gerald.gutier...@gmail.com wrote: Annoying thing is that when I try to make it happen, even if I run the script via cron (by changing the crontab over and over), it doesn't happen. Here's a really ugly workaround: echo fossil ... | at now will run it through cron immediately ;) Other than that, i can't comment: i've only seen such behaviour in 'ping' on Solaris, where it can cause a backlog of cronjobs, which causes all other jobs to queue up until you kill the pings, at which point _all_ queued jobs, since the queue limit was reached (several days in my case), run in rapid succession! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it advisable to put a .fossil repository on Dropbox?
On Wed, May 7, 2014 at 8:15 AM, Stephan Beal sgb...@googlemail.com wrote: The lock you're seeing is almost certainly your dropbox and should be harmless. sqlite locks the db as needed, and Dropbox should recognize that and not touch the file as long as it's locked (but posix locks are advisory locks, not required to be honored!). Actually, I may have tracked it down now. It turns out to be a hung fossil process. I no longer think it's due to Dropbox. I stopped using Dropbox and started syncing to a private remote server. I use cron to do a commit sync every hour, and fossil is run from a bash script via cron. It seems that after a couple of successful runs, the fossil process starts to hang. I get a bunch of them when I do ps aux, and when I kill them, the commits start working again. I've seen references to fossil hanging before (but can't find it now). Is this a known issue? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it advisable to put a .fossil repository on Dropbox?
On Thu, May 8, 2014 at 8:43 AM, Gerald Gutierrez gerald.gutier...@gmail.com wrote: I stopped using Dropbox and started syncing to a private remote server. I use cron to do a commit sync every hour, and fossil is run from a bash script via cron. It seems that after a couple of successful runs, the fossil process starts to hang. I get a bunch of them when I do ps aux, and when I kill them, the commits start working again. I've seen references to fossil hanging before (but can't find it now). Is this a known issue? You're not by chance on Solaris, are you? That's the only platform i've see which likes to occasionally hang network traffic. (Long story there, but it's quite funny one if it wasn't your system which was affected by it. ;) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it advisable to put a .fossil repository on Dropbox?
On Wed, May 7, 2014 at 8:03 AM, Gerald Gutierrez gerald.gutier...@gmail.com wrote: I have a fossil repository that I use on two machines, one at work and one at home. For this one, I'd rather not host it at an online location. So I tried to to put the fossil file on Dropbox instead so that Dropbox will automatically sync the file between the two machines. Since I've tried to do this, I occasionally get database is locked errors when trying to commit on one of the two machines. Could I be corrupting the fossil file somehow this way? Is this advisable? Assuming both computers are always connected and you only use one at a time, this shouldn't be a problem (I do this too). The problems start when you do commits on both computers without Dropbox having synced the file in between. But even then it doesn't corrupt the file, just leaves you with two copies with diverging histories. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it advisable to put a .fossil repository on Dropbox?
On Wed, May 7, 2014 at 9:46 AM, Baruch Burstein bmburst...@gmail.comwrote: On Wed, May 7, 2014 at 8:03 AM, Gerald Gutierrez gerald.gutier...@gmail.com wrote: I have a fossil repository that I use on two machines, one at work and one at home. For this one, I'd rather not host it at an online location. So I tried to to put the fossil file on Dropbox instead so that Dropbox will automatically sync the file between the two machines. Since I've tried to do this, I occasionally get database is locked errors when trying to commit on one of the two machines. Could I be corrupting the fossil file somehow this way? Is this advisable? Assuming both computers are always connected and you only use one at a time, this shouldn't be a problem (I do this too). The problems start when you do commits on both computers without Dropbox having synced the file in between. But even then it doesn't corrupt the file, just leaves you with two copies with diverging histories. +1. i've done this before (not recently), and haven't run into problems, but it should be a problem if one or another machine goes offline and work happens on both. i don't like to host checkouts in dropbox because all the temp files (*.o, *.so, etc.) sync and basically cause dropbox to thrash constantly. i've hosted repo files on dropbox before (not shared - only 1 user), that works fine. Never had a problem with it, except that the journal file might get synced (potentially causing a problem if timing is particularly bad, though i've never seen anything bad happen there). The lock you're seeing is almost certainly your dropbox and should be harmless. sqlite locks the db as needed, and Dropbox should recognize that and not touch the file as long as it's locked (but posix locks are advisory locks, not required to be honored!). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Is it advisable to put a .fossil repository on Dropbox?
I have a fossil repository that I use on two machines, one at work and one at home. For this one, I'd rather not host it at an online location. So I tried to to put the fossil file on Dropbox instead so that Dropbox will automatically sync the file between the two machines. Since I've tried to do this, I occasionally get database is locked errors when trying to commit on one of the two machines. Could I be corrupting the fossil file somehow this way? Is this advisable? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
