#693033 Applying options to sub-hierarchies only

#693033#5
Date:
2012-11-12 10:41:44 UTC
From:
To:
Part of my use case for unison is to keep my home directories in
sync between my laptop and my desktop machine. The desktop has a few
Samba mounts integrated into the hierarchy, the idea being that the
laptop gets an offline copy on sync. This works very well,
especially thanks to the follow and mountpoint keywords.

Unfortunately, the Samba server enforces 0660 permissions, while
I have a umask of 0027 on the laptop. Therefore, when I create
a file on the laptop within one of the "offline-Samba" folders and
then sync it with the desktop, it fails:

  Failed [foo/bar/43_baz.pdf]: Failed to set permissions of file
  /home/madduck/foo/bar/.unison.43_baz.pdf.05c1c66347c165b5225f4fbfb54cf19c.unison.tmp
  to rw-r-----: the permissions was set to rw-rw---- instead. The
  filesystem probably does not support all permission bits. If this
  is a FAT filesystem, you should set the "fat" option to true.
  Otherwise, you should probably set the "perms" option to 0o1757
  (or to 0 if you don't need to synchronize permissions).

I don't want to excluse permissions-syncing from the whole sync, so
what I am missing is a way to say, e.g.

  subdir_option = Path foo/bar perms = 0

which is one way to limit certain preferences to a subdirectory.

Another method might extend the mountpoint keyword:

  mountpoint = foo/bar fat

which would turn on the FAT option for the mountpoint.

Thanks,

#693033#10
Date:
2012-11-16 12:13:45 UTC
From:
To:
Hi,

your request is a feature wish and the unison manual says:

   Feature requests are welcome, but will probably just be added to
   the ever-growing todo list. They should also be sent to
   unison-users@yahoogroups.com.

The standard procedure would be that we forward your request to
unison-users@yahoogroups.com, it will be added to TODO.txt and,
very likely, nothing else will happen.

It might make more sense if you post your problem yourself to
unison-users@yahoogroups.com and ask for a workaround there. You
could, for instance, synchronize with 2 unison invocations, where
the first one uses perms = 0 and is restricted to the samba
directories.

Bye,

Hendrik