Front page

ACL and xattrib (Cancel and Replace Previous) 2

8850fe3c74fb4bb98843851c248741f9
NEWBORN EMBEZZLE WOODLARK

From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---     
   
   
   So, correct me if I am wrong but *ACL is supported and works properly*, at the very least if using the fuse method to restore.
   
   Lars or anyone else, please let me know if the problem described in my original post using the 'obnam restore' as opposed to using fuse is expected/correct, etc.; or not.
   
   Thanks and great job on obnam.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: stef <stef_204@yahoo.com>
Date: Tue, 11 Apr 2017 08:01:25 +0000 (UTC)

   I tried the fuse restore option as well, just to be sure this ACL issue was not related to the restore command (the second way of restoring files, as per the manual.)
   
   ACL state is correct here.
   
   
   /mnt % obnam mount --to obnam-fuse
   
   /mnt/obnam-fuse
    % l
   total 20K
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 .
   drwxr-xr-x 10 root root 4.0K Apr 11 09:32 ..
   drwxr-xr-x 20 root root 4.0K Apr 10 19:46 2
   lrwxr-xr-x 20 root root 4.0K Apr 10 19:46 latest -> 2
   -r--r--r-- 20 root root 4.0K Apr 10 19:46 .pid
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % l
   total 41K
   drwx------    2 obguy users 4.0K Apr 10 19:34 .
   drwx------  223 obguy users  20K Apr 10 19:46 ..
   -rwx------    1 obguy users 3.6K Apr 10 19:32 areca_run.sh
   -rw-------    1 obguy users   50 Apr 10 19:32 emacs_test.txt
   -rw-------    1 obguy users   20 Apr 10 19:32 foo.bar
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar2
   -rw-------    1 obguy users   23 Apr 10 19:32 foo.bar3
   -rw---x---+   1 obguy users   23 Apr 10 19:32 foo.bar4
   -rw-------    1 obguy users 2.1K Apr 10 19:32 jdeps.txt
   -rw-------    1 obguy users  250 Apr 10 19:32 ldap-mod.ldif
   -rw-------    1 obguy users    0 Apr 10 19:32 tbab_log.txt
   -rw-------    1 obguy users 1.5K Apr 10 19:32 test1.lyx
   -rw-------    1 obguy users  261 Apr 10 19:32 test1.tex
   -rw-------    1 obguy users   32 Apr 10 19:32 test2.tex
   -rw-------    1 obguy users 4.8K Apr 10 19:32 vnstat.png
   
   
   You can definitely see the ACl for foo.bar4.
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl foo.bar4   
   # file: foo.bar4
   # owner: obguy
   # group: users
   user::rw-
   user:test:--x
   group::---
   mask::--x
   other::---
   
   
   /mnt/obnam-fuse/2/home/obguy/test-obnam
    % getfacl -t foo.bar4
   # file: foo.bar4
   USER   obguy      rw-     
   user   test      --x     
   GROUP  users     ---     
   mask             --x     
   other            ---