public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Moshe Kaminsky <kaminsky@math.huji.ac.il>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Hints for using Unison?
Date: Mon, 1 Aug 2005 10:34:06 +0300	[thread overview]
Message-ID: <20050801073406.GA7450@kaminsky.dyndns.org> (raw)
In-Reply-To: <5bdc1c8b05073116347dcb0c62@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]

Hi,

* Mark Knecht <markknecht@gmail.com> [01/08/05 02:42]:
> 
> On 7/31/05, Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Sun, 31 Jul 2005 13:43:16 -0700, Mark Knecht wrote:
> > 
> > >    One possibly tricky part about this will be that in some cases we
> > > have found bad rips and have reripped files to fix that. In this case
> > > there is going to be a newer file in each either location with the
> > > same name but with a new size & date. Will Unison give me an option to
> > > just accept the newer one in each location and remove or backup the
> > > older one automatically?
> > 
> > Unison is particularly good at handling this sort of situation. It keeps
> > a log of the file dates each time you sync and asks for manual
> > intervention when a file have been updated on both sides since the last
> > sync.
> > 
> 
> Hi Neil,
>    OK, so I tried Unison and, twice, it just gets stuck at the same
> file. I'm running it like this:
> 
> unison /home/mark/music /mnt/Musiclib 
> 
> The gui comes up and the program gets started but then it just hangs.
> There's no obvious network activity or local disk activity. If I let
> the program sit long enough for the screensaver to kick in then when I
> unlock the screen the program is just a grey box.
> 
> So far I cannot even kill the thing. kill -9 pid or killall -9 unison
> act like they killed it but ps aux says the process is still there.
> It's even there if I try killing the gui in Gnome. The gui goes away
> but the process persists.
> 
> Any ideas on what I'm doing wrong?

This is just a guess, but I know that unison is using some lock files, 
and there might be problems with this on nfs mounted directories. I 
think the problem might be solved if you run unison on both machines, 
rather than using the mounted directory. If that's impossible, you might 
be able to change the location of the lock files by changing the root to 
a local directory.

Moshe

> 
> Thanks,
> Mark
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 

-- 
I love deadlines. I like the whooshing sound they make as they fly by. 
                                        -- Douglas Adams
    
    Moshe Kaminsky <kaminsky@math.huji.ac.il>
    Home: 08-9456841


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2005-08-01  7:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31 20:43 [gentoo-user] Hints for using Unison? Mark Knecht
2005-07-31 22:00 ` Neil Bothwick
2005-07-31 23:34   ` Mark Knecht
2005-07-31 23:52     ` Mark Knecht
2005-08-01  4:59       ` Glenn Enright
2005-08-01  5:16         ` Mark Knecht
2005-08-01  6:51           ` Glenn Enright
2005-08-01  7:42       ` Neil Bothwick
2005-08-01 15:15         ` Mark Knecht
2005-08-01 17:48           ` Mark Knecht
2005-08-01  7:34     ` Moshe Kaminsky [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050801073406.GA7450@kaminsky.dyndns.org \
    --to=kaminsky@math.huji.ac.il \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox